planlisted

# plan Create one executable source of truth, not a plan directory full of derived documents. ## Workflow 1. Read the request and any `brainstorm.md`, issue, or existing `plan.md`. Use `scout --repo` only when behavior, touchpoints, or constraints are uncertain. Research only when an external or version-sensitive fact changes the implementation choice. 2. Define the Design Contract: objective, acceptance criteria, Not Doing, constraints, assumptions, and validation strategy. 3. List work in dependency order. Use checkboxes or numbered slices in the same file; keep `plan.md` as the only plan artifact. 4. Add likely touchpoints, verification commands, material risks, and unresolved decisions. Request an independent plan review only for high-risk work or when the user asks. 5. Write `plans/YYMMDD-{slug}/plan.md` (or update the existing work item's file). Keep scout/research facts in its `Context & Evidence` section. Hand off to `cook <plan-path>` after the user approves. Do not auto-start implementation, create review artifacts, or duplicate the brainstorm record.