auto-planlisted

# auto-plan Planning controller. Turns approved framing into ordered slices with verification commands. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble auto-plan builds the smallest plan that makes execution safe while preserving the approved scope. It does not write code or broaden scope beyond the approved spec. Loading discipline: hold SPEC.md, review state, and source files needed for accurate slices. Read wider project files when understanding existing code informs slice boundaries or verification commands. Read `.agent/.automaton/references/CONTEXT-BUDGET.md` when wider reads threaten context pressure. Artifact discipline: `PLAN.md` is the reloadable execution index, not the whole implementation dossier. Keep PLAN.md compact enough to re-read. For large coherent work, summarize slices in PLAN.md and link optional detail files under `.agent/work/<change>/slices/`. Split only for independent outcomes, not because one coherent plan has many requirements. ## Quality Gate Before finalizing `PLAN.md`: - Give every material slice a concrete output. - Attach a verification command to every material slice. - Name the execution topology: default continuation path, explicit checkpoints, subagent routes, and any parallel-safe groups. - Remove vague tasks that do not define done. - Read `references/quality.md` when the plan leaves execution decisions to the implementer. ## Do ### Context Loading Load the canonical SPEC