spae-plan

Plan (SPAE)

When to use

• SPEC.md exists and needs an execution plan.
• STATE.json reports phase: plan.
• A revision cycle re-enters planning after /spec reprocesses findings.

Goal

• Convert normalized requirements into a concise, acyclic, atomic task graph while preserving strict phase and write boundaries.
• Produce .spae/current/PLAN.md, initialize task tracking in .spae/current/STATE.json, and advance the workstream to phase: inspect.

Input

Use only relevant context from:

• .spae/current/SPEC.md.
• .spae/current/STATE.json (consult references/STATE.md for field reference, directives, and phase snapshots).
• Repository source patterns, read only for codebase fit.

Never read .spae/current/VERIFY.md—not an input to this phase. Reading qualifies as content-blocking.

Workflow

1. GATE—Confirm .spae/current/SPEC.md exists and .spae/current/STATE.json reports phase: plan. Halt immediately with a clear result on failure. Make no changes.
2. ORIENT—Extract goal, requirements, testing strategy, out-of-scope items, and assumptions from SPEC.md. Capture every R-NNN item into an in-memory coverage checklist. Gather only the source patterns needed for codebase fit; never edit repository files.
3. PLAN—Decompose work to cover the spec without over-splitting.
4. ACT—Delete .spae/current/PLAN.md (ignore if absent) and clear the tasks registry in .spae/current/STATE.json to empty — unconditionally. Read the template from references/PLAN.md; consult references/prose-protocol.md before drafting task prose. Decompose work into atomic tasks numbered from T-001. Set each task's Satisfies to the R-NNN IDs it implements and its Intent to a one-line distillation of the goal those requirements serve—or, for an enabling task, the structural purpose it serves toward the plan ## Goal. Sort tasks by dependency, risk, and vertical value; each task must leave the system working.
5. VERIFY—Loop over every plan validity criterion:
   • For any R-NNN gap: return to ACT, add the missing task, then re-enter VERIFY. Treat Satisfies: none as intentional; flag empty or missing Satisfies as a scope-creep observation.
   • For any graph violation—cycle or forward-order failure: return to ACT, correct it, then re-enter VERIFY.
   • Exit only when all R-NNN items map to tasks and the graph has no violations.
   • Fail only for out-of-scope conditions.
6. PERSIST—Write .spae/current/PLAN.md. Initialize all task IDs as todo in .spae/current/STATE.json. Clear cursor to {}. Set phase: inspect. Write once, atomically. Re-read STATE.json after writing; on a field mismatch, rewrite and re-read before REPORT.
7. REPORT—Emit the result following the result directives and using the result template.