speci5.planlisted

# Plan Read a story spec and create a concrete implementation plan. Start by understanding the story and the codebase, then produce specific, actionable tasks. Only ask questions if the spec has genuine ambiguities that would lead to a wrong plan. <HARD-GATE> Do NOT implement code, modify specs, create features, or brainstorm ideas. This skill ONLY produces plan files in `.spec/features/<feature>/<story>/plan.md`. </HARD-GATE> ## Triggers Activate this skill when the user wants to: - Create an implementation plan for a story - Break a story into concrete development tasks - Understand what needs to be built for a story - Update an existing plan with revised tasks ## Rules 1. Tasks must be **specific and actionable** — not vague ("implement feature") but concrete ("Create `POST /api/auth/login` route in `src/routes/auth.ts`"). 2. Include unit test tasks as a first-class part of every plan (not optional). Tie each test task to acceptance criteria and existing test conventions. 3. If a `plan.md` already exists, update it — preserve any checked-off tasks and add/revise remaining ones. 4. Do NOT modify `story.md` or `feature.md` — those are the **specify** skill's domain. 5. Do NOT implement the code — only produce the plan. 6. **YAGNI ruthlessly** — Every task must tie back to an acceptance criterion. If it doesn't serve the story, leave it out. 7. Be tech-stack-specific: reference the actual frameworks, libraries, runtime, test runner, and folder conventions found in the