• User value (why this exists)
• System behavior (what it does)
• Explicit success condition (binary: pass / fail)

• Technical assumptions (language, runtime, environment)
• Performance or scale limits
• Safety / security boundaries
• Explicit MUST NOT list

• Functional correctness
• Stability / reliability
• Maintainability or clarity

• Normal scenarios
• Edge cases
• Failure or misuse scenarios

• ❌ Do NOT write any code
• ❌ Do NOT invent requirements not stated or implied
• ❌ Do NOT optimize or design architecture
• ✅ Surface ambiguities, assumptions, and risks explicitly
• ✅ Prefer clarity over completeness

“Waiting for confirmation to proceed to stage-execute.”