breakdown
Skill1 starsChanged 7 days agoMITView on GitHub
Splits agreed change into local, independently verifiable tickets. Use when user requests breakdown, tickets, or work slicing.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- artemnovitckii/claude-animation-skillstheir own version, first seen Nov 8, 2026
- islandhopper81/claude-skillstheir own version, first seen Nov 1, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- humzabuilds/claude-skillstheir own version, first seen Oct 20, 2026
- LucasCooperBey/claude-skillstheir own version, first seen Oct 20, 2026
- tukka25/code-breakdowntheir own version, first seen Oct 20, 2026
Used with
Projects with it also use ship, implement and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- artemnovitckii/claude-animation-skills★ 500same name
- jantichy/claude★ 52same name
- dtiger1889-ops/claude-harness-toolbox★ 31same name
- mehrad-dm/mastermind★ 23same name
- gregwebs/skills-sdlc★ 20same name
- flurdy/agent-skills★ 9same name
- int2t05/engineering-skills★ 3same name
- tukka25/code-breakdown★ 3same name
- shiggydoodah/skills★ 2same name
- LucasCooperBey/claude-skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- breakdownSkill
- find-rcSkill
- rubberduckSkill
- specSkill
- terseSkill
- breakdownSkill
- find-rcSkill
- rubberduckSkill
- specSkill
- terseSkill
- find-rcSkill
- mobile-web-fixesSkill
- rubberduckSkill
- specSkill
- terseSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read full source spec + linked local decisions.
- Very specific: line 16
Write docs/specs/<feature>/tickets/<NN>-<slug>.md unless repo prescribes another local location.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Breakdown
Read full source spec + linked local decisions. Inspect relevant context.md, Language.md, ADRs, callers/test seams. Missing source/access: report gap; never guess. Short prose, no emojis.
Draft complete vertical slices: narrow user behaviour through necessary layers + checks. Each fits fresh context, verifiable alone. Prefactor first only when needed to make slices safe.
Declare genuine blockers; no cycles. Independent work stays independent. Wide mechanical refactor exception: expand compatible form, migrate caller batches, contract after all batches. Keep checks green; if impossible, explicit integration branch + final integrate/verify ticket.
Show numbered titles, blockers, delivered behaviour. Ask granularity, missing dependencies, merges/splits. Wait for approved breakdown before writing tickets.
Write docs/specs/<feature>/tickets/<NN>-<slug>.md unless repo prescribes another local location. Start from .galicia/templates/ticket.md when present; replace every placeholder. Dependency order, one file per ticket. Preserve parent spec; link it. No external tracker. Never close parent automatically.
Each ticket: status ready; parent; what to build; blocked by numbers/titles or none; acceptance checkboxes; validation command/seam; context/ADR links. No copied glossary, fragile code recipe, or omitted cross-layer work. Prototype contract snippet allowed with provenance.
Execute ready frontier, one ticket per fresh context when practical. Report evidence before marking complete. Failure/blocker stays explicit; token target never excuses missing behaviour.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.