Task breakdown
A collection of practical AI agent skills for app development and code workflows.
npx -y skills add lteawoo/skills --skill task-breakdownAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Break requirements or design ideas into implementable work items. Use it when you need execution order, prerequisites, parallelism, and completion criteria.
SKILL.md
1.9 KB, as published. Nobody here has run it
Task Breakdown
Purpose
Break a large or ambiguous task into executable units and define the recommended order.
Core Principles
- Each task should be small enough to understand and complete in one pass.
- Every task needs a completion criterion.
- Make prerequisites and parallelism explicit.
- Separate documentation, implementation, and validation work.
- Split large work based on user value and testability, not just feature boundaries.
- Mark uncertainty explicitly instead of hiding it behind estimates.
Inputs
- Requirements or draft architecture
- Current codebase state
- Deadlines or priority information, if available
- Technical decisions that are already fixed
- Test or deployment constraints
Workflow
- Summarize the overall goal in one line.
- Split the scope into functional units.
- Divide each unit into design, implementation, and validation work.
- Identify prerequisites and dependencies.
- Separate parallelizable work from sequential work.
- Attach deliverables and completion criteria to each task.
Output Format
Task Goal
- Outcome that must be completed in this effort
Task List
- Task name
- Purpose
- Prerequisites
- Deliverables
- Completion criteria
Recommended Order
- Work to do first
- Work to do next
- Work that can run in parallel
Validation Points
- How to verify each task
- Needed tests or manual checks
Risks
- Schedule risk
- Dependency risk
- Work items that need further breakdown
When Information Is Missing
- If priorities are unclear, sort by the flow with the highest user value first.
- If the scope is too large, separate a first-pass breakdown from areas that need deeper decomposition.
- If investigation is required before implementation, represent it as separate work.