planning-and-task-breakdown
Decompose complex tasks into small, verifiable units of work.
Install
mkdir -p .claude/skills/planning-and-task-breakdown && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13096" && unzip -o skill.zip -d .claude/skills/planning-and-task-breakdown && rm skill.zipInstalls to .claude/skills/planning-and-task-breakdown
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Key capabilities
- →Decompose work into small, verifiable tasks
- →Identify existing patterns and conventions in a codebase
- →Map dependencies between components
- →Slice features vertically for implementation
- →Write tasks with descriptions, acceptance criteria, and verification steps
- →Order tasks to satisfy dependencies and ensure working states
How it works
The skill operates in a read-only plan mode to identify dependencies and then slices work vertically into small, verifiable tasks.
Inputs & outputs
When to use planning-and-task-breakdown
- →Breaking down a large feature
- →Estimating development scope
- →Mapping task dependencies
About planning-and-task-breakdown
Analyzes specifications to create a dependency-mapped plan. It identifies actionable tasks and acceptance criteria to prevent implementation mess.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
When not to use it
- →When a single-file change has obvious scope
- →When the specification already contains well-defined tasks
Limitations
- →Does not write code during planning
- →Tasks larger than 'L' size (5-8 files) should be broken down further
- →Does not automatically apply candidate pools to blueprints_template.ini
How it compares
This workflow explicitly structures tasks with acceptance criteria and verification steps, unlike a generic approach that might omit these details.
Compared to similar skills
planning-and-task-breakdown side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| planning-and-task-breakdown (this skill) | 0 | 3mo | No flags | Intermediate |
| trello | 41 | 4mo | Review | Beginner |
| executing-plans | 6 | 5mo | No flags | Intermediate |
| github-project-management | 4 | 7mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
project-clickup
incidentfox
ClickUp project management integration for incident tracking and task management
coo-advisor
alirezarezvani
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
tlc-spec-driven
tech-leads-club
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".