planlisted

# Potion Plan Inherit `${CLAUDE_PLUGIN_ROOT}/core/CORE.md`. Produces PLAN files that are executed **verbatim** by fresh agents. A plan is a prompt, not a document. **Plan-emission contract (must hold in every emitted PLAN/RUNBOOK):** - The specificity test: could a different Claude instance execute this without asking a single question? Placeholders ("TBD", "appropriate error handling", "similar to task N") are plan failures. - Frontmatter: `wave = max(deps)+1`; `files_modified` exclusive across same-wave plans; 2-3 tasks per plan. - Numbering: PLAN-NN and RUNBOOK-NN share one pool — the next number is one past the highest existing of either; never reuse a number. Before finishing, re-read each emitted plan against this block; fix in place, or regenerate it — at most once. ## The Iron Law ``` PLAN GOAL-BACKWARD, NOT FORWARD ``` Never start from "what tasks make sense?" Start from the phase goal and derive: 1. **Truths** — 3-7 user-observable statements that must be TRUE when done. 2. **Artifacts** — what must EXIST for each truth (path + what it provides). 3. **Key links** — what must be WIRED (from → to → via). This is where 80% of stubs hide: the component that's never imported, the API that's never called. ## Steps 1. Read STATE.md, PROJECT.md, and the phase's DISCUSSION.md. Decisions are locked; Deferred is untouchable. Done only when `phases/NN-slug/DISCUSSION.md` exists — absent means run /potion:discuss first. **Gate preflight:** read DISCU