// Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed implementation plans with bite-sized tasks.
| name | writing-plans |
| description | Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed implementation plans with bite-sized tasks. |
Write comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
> **For Implementation:** Use the @implement agent or `/execute-plan` prompt to implement this plan.
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
```python
def test_specific_behavior():
result = function(input)
assert result == expected
```
Step 2: Run test to verify it fails
Run: pytest tests/path/test.py::test_name -v
Expected: FAIL with "function not defined"
Step 3: Write minimal implementation
def function(input):
return expected
Step 4: Run test to verify it passes
Run: pytest tests/path/test.py::test_name -v
Expected: PASS
Step 5: Commit
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
## Remember
- Exact file paths always
- Complete code in plan (not "add validation")
- Exact commands with expected output
- DRY, YAGNI, TDD, frequent commits
## Execution Handoff
After saving the plan, offer execution:
**"Plan complete and saved to `docs/plans/<filename>.md`.**
**Ready to implement? Switch to @implement agent or use `/execute-plan` to begin."**
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute. Load plan, review critically, execute tasks in batches with verification.
Use when executing implementation plans with independent tasks. Dispatches subagents per task with two-stage review (spec then quality).
Use when encountering any bug, test failure, or unexpected behavior. Always find root cause before attempting fixes. Evidence before assertions.
Use when implementing any feature or bugfix. Write the test first, watch it fail, write minimal code to pass. Red-Green-Refactor cycle.
Use when about to claim work is complete, fixed, or passing. Run verification commands and confirm output before making any success claims. Evidence before assertions.