planning-and-task-breakdown

Breaks specifications into ordered, verifiable implementation tasks with acceptance criteria.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill planning-and-task-breakdown-qiuyi-hong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill planning-and-task-breakdown-qiuyi-hong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause agents and developers to produce tangled, unverifiable code. This Skill turns a spec or clear requirements into a written plan of small, dependency-ordered tasks, each with acceptance criteria and verification steps, so implementation proceeds reliably one slice at a time. ## Core Features & Use Cases - Dependency-aware task ordering: Maps the dependency graph (schema, API, UI) and slices work vertically so each task delivers a working, testable feature path. - Structured task format: Every task includes acceptance criteria, verification commands, dependencies, files likely touched, and a size estimate (XS through XL, with XL flagged for further breakdown). - Plan and task list outputs: Writes a plan document to tasks/plan.md and records tasks in tasks/todo.md or an external tracker like GitHub Issues, Jira, or Linear, with checkpoints between phases. - Use Case: You have a spec for a user registration feature. The Skill produces a plan with tasks like "user can create an account" spanning schema, API, and UI, each with testable acceptance criteria and a checkpoint after the foundation phase. ## Quick Start Ask the agent to read the spec and break the work into an ordered task list saved to tasks/plan.md and tasks/todo.md before writing any code.

Frequently Asked Questions about planning-and-task-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a large feature spec into implementable tasks?

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Give every task acceptance criteria, verification steps, dependencies, and a size estimate, and split anything larger than about five files.

What is vertical slicing in task breakdown?

Vertical slicing builds one complete feature path at a time, such as registration spanning schema, API, and UI, instead of building all of one layer first. Each slice leaves the system in a working, testable state.

Can I use GitHub Issues or Jira instead of a markdown task list?

Yes. If the project's agent rules or the user designate an external tracker, create one tracker item per task instead of writing tasks/todo.md. Map acceptance criteria into the item body, record dependencies via the tracker's linking mechanism, and note the tracker in tasks/plan.md.

When should a task be broken down further?

Break a task down when it exceeds one focused session, needs more than three acceptance criteria bullets, touches two independent subsystems, or its title contains "and". Tasks sized L (5-8 files) or XL should be split; agents perform best on S and M tasks.

What happens if a tasks/plan.md file already exists?

The Skill never overwrites an incomplete plan. If the existing file has unchecked tasks for the same work, it updates in place; for different work, it stops and asks the user rather than deleting or renaming the existing plan.