| name | planning-implementation |
| description | Generates detailed implementation plans for complex coding tasks. Use when the user has requirements but needs a structured plan before coding. |
Planning Implementation
When to use this skill
- When the user has a spec or requirements for a multi-step task.
- Before writing any code for a complex feature.
- When you need to break down a large task into bite-sized steps.
Workflow
Instructions
Assumptions: Write plans implementation assuming the engineer has zero context. Document everything: files to touch, code to write, tests to run.
Bite-Sized Task Granularity:
Each step is one atomic action:
- "Write the failing test"
- "Run it to make sure it fails"
- "Implement the minimal code"
- "Run the tests and make sure they pass"
- "Commit"
Plan File Location: docs/plans/YYYY-MM-DD-<feature-name>.md
Plan Header Template:
# [Feature Name] Implementation Plan
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
Task Structure Template:
### Task N: [Component Name] (e.g., Backend Handler / Frontend Component)
**Files:**
- Create: `backend/internal/handlers/v1/new_handler.go`
- Modify: `frontend/app/(customer)/profile/page.tsx`
**Step 1: Write the failing test / Define Interface**
Define the DTO or Service interface first.
**Step 2: Implement Logic / UI**
Follow the established patterns (Clean Architecture for Backend, shadcn/ui for Frontend).
**Step 3: Verification**
Run: `go test ./...` or `npm run dev` and manual check.
**Principals**:
- Exact file paths always.
- Complete code in plan.
- Exact commands with expected output.
- DRY, YAGNI, TDD.
