01
It starts by itself
spec gets approved. Runs in Claude Code routine or GitHub Actions.
- ↻ spec gets approved
spec file merged or marked approved
Addy Osmani · 62K installsAnthropic · Claude Code · Learning JavaScript Design PatternsPlanning and Task Breakdown skill
Runs by itself, spec gets approved.
Turn each spec into small tasks.
Install the Planning and Task Breakdown skill and make it a habit: follow https://gethabit.dev/skills/addyosmani/planning-and-task-breakdown.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
62K installs109K starsMIT licenceSource on GitHub ↗
Planning and Task Breakdown
by Addy Osmani · 62K installs
The skill
The planning and task breakdown skill by Addy Osmani turns a spec into small, ordered, verifiable tasks with acceptance criteria, dependencies and checkpoints.
Only when you ask.
The habit
Turn each spec into small tasks.
↻ Runs by itselfspec gets approved
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
Stops after one spec per run and one retry of the checks.
- 01
Plan mode
Read the spec and code without writing any code, and note risks and unknowns.
- 02
Map dependencies
Draw what depends on what so foundations come first.
- 03
Slice vertically
Cut the work into complete feature paths instead of layers.
- 04
Write tasks
Give each task a description, acceptance criteria, verification, dependencies, likely files and a size.
- 05
Order and checkpoint
Put risky tasks early and add a checkpoint after every two or three tasks.
- 06
Check old plans
If tasks/plan.md still has unchecked tasks for other work, stop and ask you.
- 07
Get approval
Save the files or tracker items and ask you to review the plan.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only intasks/**
- Talks tono outside service
- Sendsnothing
- Your OKIt asks you before anything goes out.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the Planning and Task Breakdown skill helps.
Use it when
- ✓ You have a spec and need tasks
- ✓ A task feels too large to start
- ✓ Work will run across several agents or sessions
Skip it when
- – The change is one file with obvious scope
- – The spec already holds well-defined tasks
Planning and Task Breakdown skill, answered.
Can it use GitHub Issues or Linear instead of a file?
Yes. If your project rules name a tracker, each task becomes one tracker item and tasks/plan.md lists their links.
What if a task is too big?
Size L and above gets split again. The skill aims for S and M tasks.
How do I install the Planning and Task Breakdown skill?
Copy the prompt at the top into your agent. It installs the skill from addyosmani/agent-skills and sets up the habit. Or run npx skills add addyosmani/agent-skills --skill planning-and-task-breakdown.
Is the Planning and Task Breakdown skill free?
Yes. It is published under MIT. Habit is free too.
Planning and Task Breakdown. Now as a habit.
Install the Planning and Task Breakdown skill and make it a habit: follow https://gethabit.dev/skills/addyosmani/planning-and-task-breakdown.md
All Addy Osmani skills →More planning skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by Addy Osmani, published under MIT. Habit links to the original and never changes it. Is this your skill?