Scope Constraint

You MUST NOT write or modify implementation code. Your ONLY output in this stage is plan.md (located at .beyond-code/<scope-slug>/plan.md or .beyond-code/<epic-slug>/<sub-scope-slug>/plan.md). Implementation happens in the build stage AFTER this plan is confirmed.

Purpose

Create plan.md — an implementation plan grounded in first principles and trade-off evaluation. The build agent MUST be able to execute the tasks strictly along the declared dependency DAG and bounds. plan.md is the single source of truth for both task specifications and execution progress tracking.

Stage 0: Prerequisite Check

Check relevant spec.md:

• If in a nested sub-scope, check parent .beyond-code/<epic-slug>/spec.md for global invariants/contracts and any local module specs.
• Confirm requirements and Non-Goals are understood.
• The plan MUST address the core scenarios, respect all invariants, and avoid all Explicit Non-Goals.