breakdown
/breakdown
Splits agreed change into local, independently verifiable tickets. Use when user requests breakdown, tickets, or work slicing.
- Author
- mrlemoos ↗
- Repository
- galicia ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Splits agreed change into local, independently verifiable tickets. Use when user requests breakdown, tickets, or work slicing.
Original author description
Splits agreed change into local, independently verifiable tickets. Use when user requests breakdown, tickets, or work slicing.
How it works
SKILL.md has no level-two headings · 17 lines, 200 words
SKILL.md preview
--- name: breakdown description: Splits agreed change into local, independently verifiable tickets. Use when user requests breakdown, tickets, or work slicing. --- # 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mrlemoos/galicia | 81 | MIT |
| userKael/rastro | 100 | MIT |
| lamngockhuong/aiteamkit | 100 | MIT |
| artemnovitckii/claude-animation-skills | 100 | MIT |
| mehrad-dm/mastermind | 100 | MIT |
Database snapshot: 13.11.2026 · package version 8bd5c95c51bd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100writing-plans
Use when the approach is agreed and the change takes more than a couple of steps. Breaks the work into small, independently verifiable tasks with exact files and verification commands, so execution needs no guesswork. - 86to-tickets
Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker. - 100to-tickets
Break a spec, plan or the current conversation into tracer-bullet tickets, each with acceptance criteria and the tickets that block it. Shows the breakdown, then publishes it with the tracker operations in docs/agents/issue-tracker.md after the user approves. Use when a plan or… - 100ticket-breakdown
Use when the user wants a PRD or design doc broken into tracker-ready epics and tickets for a team to pick up: work breakdown, Jira tickets, or Linear issues, rather than implemented now. - 95work-breakdown
Convert a feature, refactor, or migration objective into work-unit tickets with acceptance checks and dependencies. Use for backlog preparation or ticket creation rather than implementation. - 100feature-spec-breakdown
Breaks a feature spec and its plan into small, independent vertical-slice tickets saved as Markdown files, checks coverage against both, reviews tickets one by one, then optionally creates todos or publishes to a tracker the user names. Use when asked to break down, split, or…