spae-planlisted

# 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 empt