planlisted

# Plan Turn an approved SpecScore Feature (or Idea) into a lint-clean, ordered task list. ## Hard Gate <HARD-GATE> Do NOT invoke `specstudio:implement`, `writing-plans`, `frontend-design`, `mcp-builder`, or ANY implementation skill until ALL of the following are true: 1. The Plan artifact exists at `spec/plans/<slug>.md` and contains at least one `### Task N: <name>` task inside the `## Tasks` section. 2. Every acceptance criterion in the source Feature is either covered by ≥1 task (via the task's `**Verifies:**` line) OR explicitly listed under `## Deferred AC Coverage` with a concrete one-sentence reason. *(Skip in Idea-sourced mode — there are no ACs.)* 3. `specscore spec lint` passes. 4. The plan-document reviewer subagent returned `Approved`. 5. The user has explicitly approved the written Plan. The only skill invoked after `specstudio:plan` is `specstudio:implement` (or — while `implement` is unshipped — a hand-back to the user with that recommendation). </HARD-GATE> ## When to Use - A SpecScore Feature is `**Status:** Approved` and the user is ready to decompose it into work. - A SpecScore Idea is `**Status:** Approved` and the user wants to plan directly from it without a Feature. - The event `feature.approved` has fired and the user has confirmed they want to plan. - The user wants to revise an existing approved Plan (revise-in-place by default). **Refuse and redirect when:** - The source Feature is `Draft` or `Under Review` → tell the user to run `