plan-strictlisted

# Plan Strict Forward-design a strict-granularity plan for the active thread. You gather the thread's context, draft an index plus one dispatchable brief per task — each brief carrying explicit substeps, files modified, verification, and acceptance criteria — self-review before emission, create this invocation's plan folder, write the index and the task briefs into it, then confirm the path. Run end-to-end without walking the user task-by-task. Writing the files is where you stop. ## Inputs Gather all of these before drafting; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the design. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - **The design the plan implements** — the primary input, in one of two accepted forms. The thread's **`spec.md`** is the form when the file exists, and it is the plan's authority: its intended goal, expected behavior, and constraints drive the task list directly, its acceptance criteria map cleanly onto per-task acceptance criteria, and its degrees-of-freedom section tells the plan which *hows* are open. When the invocation names a **referenced artifact** instead — a repository path, a GitHub issue (a full `https://github.com/<owner>/<repo>/issues/<NNN>` URL or the short `owner/repo#NNN` form), another thread's artifact read as history, or the user's own prompt when nothing else is named — that refer