Use when you have a spec or requirements for a multi-step task, before touching code
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. 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.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Context: This should be run in a dedicated worktree (created by brainstorming skill).
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 Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
**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**
```python
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**
```bash
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```
After saving the plan, offer execution choice:
"Plan complete and saved to docs/plans/<filename>.md. Two execution options:
1. Subagent-Driven (this session) - I dispatch fresh subagent per task, review between tasks, fast iteration
2. Parallel Session (separate) - Open new session with executing-plans, batch execution with checkpoints
Which approach?"
If Subagent-Driven chosen:
If Parallel Session chosen:
CRITICAL THEMATIC RULE: You are working inside the superpower-with-files unified framework.
🚀 **SUPERPOWER ACTIVE:** spf-write-plancomplexity: simple | medium | complex to the plan header.
simple: Combine boilerplate and logic into fewer, larger tasks. Keep all instructions in active_tdd_plan.md.medium/complex: Use the Split Architecture.active_tdd_plan.md MUST remain a concise high-level task list..superpower-with-files/guides/task-N.mdGuide: See guides/task-N.md.Depends on: [Task ID | None]Parallel with: [Task ID | None]Cargo.toml -> cargo testpyproject.toml -> pytestpackage.json -> npm test(optional).templates/ directory to guide choices."Planning phase complete. The plan and guides have been saved to [.superpower-with-files/]. Please review. To proceed, use: 'Execute the plan.'"
task_plan.md, active_tdd_plan.md, findings.md, progress.md), you MUST append a horizontal rule and a timestamp at the very bottom:
---
*Last Updated: YYYY-MM-DD HH:MM UTC*complexity: simple | medium | complex to the plan header.
simple: Combine boilerplate and logic into fewer, larger tasks.complex: High granularity, minute-by-minute steps.Cargo.toml -> cargo testpyproject.toml / pytest in requirements.txt -> pytestpackage.json -> npm test(optional) (e.g., Step 5: Verify structure (optional)).templates/ directory within this skill and use the corresponding template to guide your project structure and library choices.projects/tgnews"), you MUST honor that path immediately..superpower-with-files/active_tdd_plan.mddocs/plans/ unless specifically requested by the user.ZIP package — ready to use