Menu

Individual skill

breakdown

0upvotes

Break an epic or a design document into owned, sequenced tasks: one deliverable each, an owner, a dependency order, the parallel lanes that avoid two people editing the same file, and a definition of done per task. Use before a sprint starts, when work has to be shared across several developers, or when a piece of work needs owners and parallel lanes. Work that stays with one person is planned with `atk:plan` instead, however many days it takes. Triggers on: "break down", "breakdown", "chia task", "phân chia công việc", "split this epic", "task list", "WBS", "タスク分解", "who does what", "assign tasks", "/atk:breakdown".

plugins/atk/skills/breakdown/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
12
Repository last updated
Nov 9, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

# Task Breakdown (`atk:breakdown`)

Turns one large piece of work into tasks a team can run at the same time without colliding. The
value is in the dependency order and the file ownership, not in the list itself.

## Scope

Handles: decomposing an epic or design into tasks, assigning an owner to each, ordering by
dependency, grouping into parallel lanes with explicit file ownership, and writing a per-task
definition of done.

Does NOT handle: sizing (`atk:estimate`), designing the solution (`atk:design-doc`), or
implementation. It divides work between people; how one person's share is then carried out, in
phases and steps, is `atk:plan`, which the assignee writes for themselves afterwards. Work that
Back to top