plan-brieflisted

# Plan Brief Turn the thread's design into a short, one-screen plan that gives implementation a sensible order and a way to check the result. You gather the thread's context, draft the plan body, create this invocation's plan folder, write its `plan.md`, and confirm the path. Writing the file is where you stop — do not stage, commit, or push. A brief plan trades depth for speed: it orders the work and records overall verification. When the work genuinely needs more rigor than that, recommend `plan-strict` instead of inflating the brief plan (see `## When to recommend plan-strict`). ## 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. When the invocation names a **referenced artifact** instead — a repository path, a GitHub issue, another thread's artifact read as history, or the user's own prompt when nothing else is named — that reference is the form; it is material, and it carries no authority over a `spec.md` the thread holds. - The thread's `seed.md` — why the thread exists and what triggered it. - The thread's `adr/` and `glossary.md` — the thread