breakdown SKILL.md skillA
breakdown from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/breakdown@git:20261014.03c655ePins git:20261014.03c655e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/breakdown/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.03c655e, committed Oct 14, 2026
- First version recorded
- Oct 1, 2026
- Size
- 5,547 bytes
- Repository stars
- 9
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 belongs to one person needs no breakdown first, however many days it takes. It also does not decide who works on what: it proposes, the PM and Tech Lead assign. ## Roles Tech Lead proposes the split. PM confirms owners and order. Each Dev owns their tasks. QA gets its own test tasks in the same list, not a single "testing" task at the end. See `shared/team-roles.md`. ## Invocation ```bash /atk:breakdown <design-path> # Break down from a technical design document …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/breakdown@sha256:2996f797c5ec99a5The line at the top of this page pins the label git:20261014.03c655e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4aqfpk3boadgj5va)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 1, 2026 and Oct 14, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.03c655e latest | 2026-10-14 | 03c655e | 5,547 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 5,336 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5547 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lamngockhuong/aiteamkit · 9 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4aqfpk3boadgj5va GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/breakdown GET https://markdownregistry.com/api/v1/blob/2996f797c5ec99a5186ceffa9f576907c7af4f6cab11e6e9ef6bd33598214acf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit