plan

# Create Implementation Plan This is a primary-session artifact skill. The user-started conversation creates the plan and task files, then the user manually switches that same conversation to an implementation model to execute them. Translate a feature spec into a concrete, phased implementation plan saved under `docs/plans/<feature>/`. Plans and task files are committed implementation records for the current buildout; specs remain the durable requirements under `docs/specs/`. ## Input - The feature spec (`docs/specs/<slug>/spec.md`) — read it first - The codebase — explore relevant areas before designing ## Output - `docs/plans/<slug>/plan.md` — a structured plan that links back to the spec and references every task file - `docs/plans/<slug>/task-<NN>-<short-slug>.md` — one independently executable implementation task per file --- ## 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. Map dependencies before writin...