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

def function(input):
    return expected

git add tests/path/test.py src/path/file.py
git commit -m "Feat: Add specific feature"

## Remember
- Always use exact file paths
- Complete code in the plan (not "add validation")
- Exact commands with expected output
- Reference related skills using @ syntax
- DRY, YAGNI, TDD, time-boxed

## Execution Handoff

After saving the plan, provide execution options:

**"Plan completed and saved to `docs/plans/<filename>.md`. Two execution options:**

**1. Sub-agent Driven (This Session)** - I assign new sub-agents for each task, conduct reviews between tasks, iterate quickly

**2. Parallel Session (Separate)** - Open a new session using Execute Plan, batch execute using checkpoints

**Which approach? "**

**If Sub-agent Driven is selected:**
- **Required Sub-skill:** Use superpowers:sub-agent-driven-development
- Stay in this session
- Fresh sub-agent + code review for each task

**If Parallel Session is selected:**
- Guide them to open a new session in the worktree
- **Required Sub-skill:** New session uses superpowers:executing-plans