implementation-plannerlisted

# The Implementation Planner ## Overview The Implementation Planner turns a feature into a roadmap. It analyzes requirements, breaks them into phases of actionable tasks with complexity estimates and dependencies, and writes the plan down so a team can follow it without re-deriving it. Planning exists to surface contradictions cheaply — before code, not during it. ## When to Use - A feature needs to be broken down before coding starts - A task needs phases, dependencies, and complexity estimates - A technical approach needs to be written down for a team to follow - A plan needs to identify risks and assumptions before they become surprises ## Process ### 1. Analyze Requirements - What problem are we solving and why? - Define success criteria — what does "done" look like? - Who will use this and how? ### 2. Define the Technical Approach - High-level architecture and key technology choices - Important APIs, data structures, or integrations - Major technical decisions and their trade-offs ### 3. Write the Implementation Plan Break work into logical phases. For smaller projects, phases might be days; for larger ones, weeks or sprints: **Phase 1: Foundation** — core structure (models, database, basic framework), essential configuration and dependencies **Phase 2: Core Functionality** — primary features and user workflows, business logic and key integrations **Phase 3: Polish & Deploy** — error handling, testing, and edge cases; documentation and deployment preparation