planlisted

**big work gets staged before it starts:** one PR per stage, ordered once instead of mid-build - written before complex or architectural work, never after it - the checklist is the deliverable, and readiness is what gates it - a stage nobody can run is a stage that does not start # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/plan/plan.sh "$ARGUMENTS" echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran, so there is no command to issue - fail (`sidecar exit` > 0) → abort and report the raw terminal error inside a markdown code block - `collision: yes` → STOP and name the file already holding that slug; never overwrite a plan - `spec: <path>` → the argument was a graph spec; read it whole before step 1 and treat it as the brief - success (`sidecar exit` = 0) → take `target` from the telemetry and continue to step 1 1. gather what the plan rests on before drafting a line of it - read the repo for the motivation, the obstacle, the constraint and the guardrails - with `spec: <path>`, read the spec whole first; its `CONTEXT:` is answered and is never re-asked - ASK the user for whatever the repo cannot answer, in one round, then WAIT for the answers - the round is lettered `a.`, `b.`, `c.`, in one fenced block, with no prose between the rows - verify any claim carrying a number before it lands, or leave the number out 2. release the user before writing a line, in o