plan-writing

Topics in the source

• Plan Writing
• Overview
• Task Breakdown Principles
• 1. Small, Focused Tasks
• 2. Clear Verification
• 3. Logical Ordering
• 4. Dynamic Naming in Project Root
• Planning Principles (NOT Templates!)

Source: obra/superpowers This skill provides a framework for breaking down work into clear, actionable tasks with verification criteria. Each task should take 2-5 minutes One clear outcome per task Independently verifiable How do you know it's done? What can you check/test? What's the expected output? Dependencies identified Parallel work where possible Critical path highlighted Phase X: Verification is always LAST Plan files are saved as {task-slug}.md in the PROJECT ROOT Name derived from task (e.g., "add auth" → auth-feature.md) NEVER inside .claude/, docs/, or temp folders 🔴 NO fixed templates. Each plan is UNIQUE to the task. | ❌ 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. -- | ❌ 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. -- Fo

This is an excerpt. Refer to the complete source and its current requirements.