plan-writing

Plan Writing

> Source: obra/superpowers

Overview

This skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.

Task Breakdown Principles

1. Small, Focused Tasks

2. Clear Verification

3. Logical Ordering

4. Dynamic Naming in Project Root

Planning Principles (NOT Templates!)

> 🔴 NO fixed templates. Each plan is UNIQUE to the task.

Principle 1: Keep It SHORT

| ❌ Wrong | ✅ Right |

|----------|----------|

| 50 tasks with sub-sub-tasks | 5-10 clear tasks max |

| Every micro-step listed | Only actionable items |

| Verbose descriptions | One-line per task |

> Rule: If plan is longer than 1 page, it's too long. Simplify.

---

Principle 2: Be SPECIFIC, Not Generic

| ❌ Wrong | ✅ Right |

|----------|----------|

| "Set up project" | "Run npx create-next-app" |

| "Add authentication" | "Install next-auth, create /api/auth/[...nextauth].ts" |

| "Style the UI" | "Add Tailwind classes to Header.tsx" |

> Rule: Each task should have a clear, verifiable outcome.

---

Principle 3: Dynamic Content Based on Project Type

For NEW PROJECT:

For FEATURE ADDITION:

For BUG FIX:

---

Principle 4: Scripts Are Project-Specific

> 🔴 DO NOT copy-paste script commands. Choose based on project type.

| Project Type | Relevant Scripts |

|--------------|------------------|

| Frontend/React | ux_audit.py, accessibility_checker.py |

| Backend/API | api_validator.py, security_scan.py |

| Mobile | mobile_audit.py |

| Database | schema_validator.py |

| Full-stack | Mix of above based on what you touched |

Wrong: Adding all scripts to every plan

Right: Only scripts relevant to THIS task

---

Principle 5: Verification is Simple

| ❌ Wrong | ✅ Right |

|----------|----------|

| "Verify the component works correctly" | "Run npm run dev, click button, see toast" |

| "Test the API" | "curl localhost:3000/api/users returns 200" |

| "Check styles" | "Open browser, verify dark mode toggle works" |

---

Plan Structure (Flexible, Not Fixed!)

# [Task Name]

## Goal
One sentence: What are we building/fixing?

## Tasks
- [ ] Task 1: [Specific action] → Verify: [How to check]
- [ ] Task 2: [Specific action] → Verify: [How to check]
- [ ] Task 3: [Specific action] → Verify: [How to check]

## Done When
- [ ] [Main success criteria]

> That's it. No phases, no sub-sections unless truly needed.

> Keep it minimal. Add complexity only when required.

Notes

[Any important considerations]