Overview
Write a comprehensive implementation plan 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, tests, documentation they may need to check, how to test it. Hand them the whole plan as small tasks. DRY. YAGNI. TDD. Commit frequently.
Assume they are a skilled developer but know almost nothing about our toolset or problem domain. Assume they don't know much about good test design.
Announce at the start:"I'm using the Writing Plans skill to create an implementation plan."
Context: This should operate in a dedicated worktree (created through the brainstorming skill).
Save the plan to:docs/plans/YYYY-MM-DD-<feature-name>.md
Bite-sized task granularity
Each step is one action (2-5 minutes):
- "Write failing test" - step
- "Run it to make sure it fails" - step
- "Implement the minimal code to make the test pass" - step
- "Run tests and make sure they pass" - step
- "Commit" - step
Plan Document Header
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 Structure
### 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():
結果 = 函數（輸入）
斷言結果==預期
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函數（輸入）：
預期回報
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“壯舉：新增特定功能”
## 記住
- 始終精確的文件路徑
- 計劃中的完整代碼（不是“添加驗證”）
- 具有預期輸出的精確命令
- 用@語法參考相關技巧
- DRY、YAGNI、TDD、間隙空間
## 執行交接
保存計劃後，提供執行選擇：
**“計劃完成並保存到`docs/plans/<filename>.md`。兩種執行選項：**
**1.子代理驅動（本次會議）** - 我為每個任務分配新的子代理，在任務之間進行審查，快速迭代
**2.並行會話（單獨）** - 使用執行計劃打開新會話，使用檢查點批量執行
**哪一種方法？ ”**
**如果選擇子代理驅動：**
- **所需的子技能：** 使用超能力：子代理驅動開發
- 留在本次會議
- 每個任務新鮮的子代理+程式碼審查
**如果選擇並行會議：**
- 引導他們在工作樹中打開新會話
- **所需的子技能：** 新會話使用超能力：執行計劃