planlisted

# Create Implementation Plan Translate a feature spec into a concrete, phased implementation plan saved as `plan.md` alongside the spec. ## Input - The feature spec (`docs/specs/<slug>/spec.md`) — read it first - The codebase — explore relevant areas before designing ## Output `docs/specs/<slug>/plan.md` — a structured plan the implementing agent can follow directly --- ## Steps ### 1. Read the spec Read `docs/specs/<slug>/spec.md` in full. Identify: - The observable behaviors (What section) - The scenarios — each is a potential test case - Any out-of-scope items (don't plan for these) ### 2. Explore the codebase Search in parallel for all integration points the spec touches: - Relevant models, repos, services, handlers - Similar existing features to reuse as patterns - Frontend state slices, hooks, and components in the area - Existing tests in the area (to understand the testing patterns) Use `docs/decisions/INDEX.md` to check for relevant architectural decisions. ### 3. Ask before designing (if needed) If the spec leaves implementation choices open, ask — one question at a time. Do not assume. Examples of things to ask: - Which table/model owns new data? - Is a new API endpoint needed or does an existing one extend? - Should this be behind a feature flag? Stop asking when you have enough to write the plan. ### 4. Write plan.md Save to `docs/specs/<slug>/plan.md`. Use this structure: ```markdown --- spec: <slug> created: YYYY-MM-DD status: draft --- # Imp