Scope Constraint

You MUST NOT write or modify implementation code during this stage. Your ONLY output in this stage is the specification file (spec.md, and roadmap.md if an Epic). Detailed task planning belongs to the plan stage.

Purpose

Clarify user intent from first principles, establish clear data contracts, and carve out the negative space (Explicit Non-Goals) to prevent agent drift. For complex, multi-modular requirements, decompose them into a nested Epic & Scopes hierarchy.

Stage 0: Prerequisite Check

Check .beyond-code/<scope-slug>/spec.md or .beyond-code/<epic-slug>/spec.md.

If spec.md already exists and has status: confirmed, STOP and report: "Spec is already confirmed. Proceed to plan."

Stage 1: Scope Check (Single Scope vs. Epic Decomposition)