Individual skill

task-breakdown-assistant

Breaks a single ticket or task into concrete, actionable subtasks. Use when one task feels too large or vague to just start on, at the individual-task level - not whole-project planning.

skills/productivity/task-breakdown-assistant/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Aug 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 1,338 bytes
SKILL.mdcore · 2,275 bytes
examples/example.mddoc · 1,912 bytes

Read excerpt


## Purpose

Break one task/ticket down into concrete, sequenced subtasks small enough to just start on. Deliberately atomic and single-task scoped — for whole-project phasing and cross-team dependencies, see [Project Planner](../../architecture/project-planner/) instead.

## When to Use

- A single ticket/task feels too large or vague to start on directly.
- Estimating a task requires understanding its real sub-steps first.
- Handing a task to someone else and want to leave them a concrete starting checklist.

Differs from [Project Planner](../../architecture/project-planner/): that skill produces phases/milestones for a multi-task project; this skill produces the subtask checklist for one task within that project.

## What to Analyze / Do