Skip to content
SkillModel-led2,395 tokens in use

planning-and-task-breakdown

Turn a spec into ordered, vertically sliced tasks with acceptance criteria, dependencies and checkpoints.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/planning-and-task-breakdown
npx skills add addyosmani/agent-skills --skill planning-and-task-breakdown
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing planning-and-task-breakdown costs

57tokens idle
2,395tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Planning and Task Breakdown guides an agent from a spec to a task list it can execute. The agent first works in a read-only plan mode, maps the dependency graph, slices the work vertically and writes each task with acceptance criteria, verification steps, dependencies and likely files.

Tasks are ordered so risk comes early, with checkpoints after every two or three tasks. The plan goes to tasks/plan.md and the task list to tasks/todo.md or a designated external tracker, and an incomplete plan is never overwritten without asking.

What You Get

  • A five-step planning process
  • A task template and checkpoint template
  • A plan document template with risks and open questions
  • Parallelization guidance and a verification checklist

Common Use Cases

  • Breaking a spec into implementable tasks
  • Splitting a task that feels too large
  • Ordering work by dependency and risk
  • Recording tasks in an external tracker

What Makes It Unique

The skill protects existing plans: it checks for unchecked tasks before writing and stops to ask when the new work differs. It also maps the same task structure onto an external tracker and keeps plan.md as an index of tracker items.

Under The Hood

The skill is a single SKILL.md of instructions. The agent reads the spec and codebase in a read-only phase, then writes tasks/plan.md and tasks/todo.md, creating the tasks folder if needed. With a designated tracker it creates items there. It runs no scripts.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers