plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
Profile →npx skills add sickn33/agentic-awesome-skills --skill plan-writing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. -
- Overview
- Task Breakdown Principles
- 1. Small, Focused Tasks
- 2. Clear Verification
- 3. Logical Ordering
- 4. Dynamic Naming in Project Root
- Planning Principles (NOT Templates!)
- Principle 1: Keep It SHORT
- Principle 2: Be SPECIFIC, Not Generic
- Principle 3: Dynamic Content Based on Project Type
- Principle 4: Scripts Are Project-Specific
- Principle 5: Verification is Simple
- Plan Structure (Flexible, Not Fixed!)
- Notes
What does the plan-writing skill do?
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill plan-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.