Agent skill · writing content · aiskillstore
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
Why this skill is useful
Provides a structured framework for task planning that includes specific verification criteria and dynamic content based on project type, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 Each task should take 2-5 minutes One clear outcome per task Independently verifiable 2. Clear Verification How do you know it's done? What can you check/test? What's the expected output? 3. Logical Ordering Dependencies identified Parallel work where possible Critical path highlighted Phase X: Verification is always LAST 4. Dynamic Naming in Project Root 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 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: What tech stack? (decide first) What's the MVP? (minimal features) What's the file structure? For FEATURE ADDITION: Which files are affected? What dependencies needed? How to verify it works? For BUG FIX: What's the root cause? What file/line to change? How to test the fix? --- Principle 4: Scripts Are Project-Specific 🔴 DO NOT copy-paste script commands. Choose based on project type. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/plan-writing