writing-plans

# [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]

### 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

def function(input):
    return expected

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
- Reference relevant skills with @ syntax
- DRY, YAGNI, TDD, frequent commits
 
## Execution Handoff
 
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:**
- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development
- Stay in this session
- Fresh subagent per task + code review
 
**If Parallel Session chosen:**
- Guide them to open new session in worktree
- **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plans
 
## When to Use
This skill is applicable to execute the workflow or actions described in the overview.
 
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.