Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fbarrento/spec-breakdown
Turns an approved spec into ordered, independently mergeable implementation issues, and drafts the capability README update that keeps the repo the source of truth. Use after a change has been specced and its spec approved. Refuses to run without an approved spec. The last skill in the product pipeline.
Passed 16 of 21 test cases with the skill, and 5 of 21 without it.
and 11 more in the full report
12 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Should write logic L2b execute before read contracts L2a in the issue sequence so state mutations are available first?
| Checked | Without skill | With skill |
|---|---|---|
| Orders L2a read contracts to precede L2b write logic in issue sequencing. | Missed | Passed |
The instructions your model reads when the skill loads.
spec-breakdown produces issues.md — the ordered implementation issues for
one change — from an approved spec. It assigns each of the spec's building
blocks to a dependency-role layer, splits each layer into independently
mergeable issues, attaches a completion contract and a review weight to each,
and drafts the capability README.md update the change makes true. It is the
last pipeline skill: after it, implementation is the code STOP gate in
laravel-rules / inertia-rules.
Generic skill — hard-codes no path. Resolve the state-tree root from the
project's CLAUDE.md (project-declared paths, DESIGN_PRODUCT_PIPELINE.md §2);
default docs/, and say which you used. {capabilities-root} means
{declared-root}/capabilities (default docs/capabilities).
Before producing issues you MUST, in order:
spec.md (or
spec-{n}-{slug}.md files if split). Usable ONLY if frontmatter has
status: approved with approved_by and approved_on populated. If
draft, unapproved, or invalidated by a later edit — STOP; the spec needs
(re-)approval via change-spec first.change-spec problem.issues.md.Hard rules:
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.