plan-strictlisted

# Plan Strict Forward-design a strict-granularity plan for the active thread from a single upstream input. Read the input, draft an index plus one dispatchable brief per task — each brief carrying explicit substeps, files modified, verification, and acceptance criteria — self-review before emission, write the index `plan.md` at the thread root and the task briefs under `plan-tasks/`, then confirm the path. Run end-to-end without walking the user task-by-task. Writing the files is where you stop. ## Inputs Accept ONE of the following input forms. Detect which form was passed before drafting: 1. **A spec artifact** — the thread-root `spec.md`, the usual upstream input. Its semantic-contract elements (intended outcome, expected behavior, constraints, acceptance guidance) drive the plan's 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. 2. **A proposal artifact** — the thread-root `proposal.md`. When the input is a proposal rather than a spec, the plan tasks elaborate the proposal's rough shape into an implementable sequence; treat the proposal's open questions as items the plan either resolves or carries forward. A thin proposal yields a thin plan — if there is not enough substance to warrant per-task briefs, flag it in self-review rather than padding the structure. 3. **The thread's durable inputs** — `decisions.md` (the settled decisions the plan must honor) t