Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fbarrento/change-spec
Turns an approved PRD into a technical spec — the HOW of one change to a capability. Use after a change has been scoped and its PRD approved, to decompose it into building blocks and route each to its governing rule file. Refuses to run without an approved PRD. Cites rule-file paths; never restates rule content.
Passed 13 of 18 test cases with the skill, and 4 of 18 without it.
and 13 more in the full report
11 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before routing building blocks for `docs/capabilities/notifications/changes/0002-slack-integration/prd.md`, we see an ADR titled `ADR-004-queue-drivers.md`. Can we rely on the document title to determine if it constrains our change?
| Checked | Without skill | With skill |
|---|---|---|
| Mandates reading the decision record document body in full rather than relying on titles or commit messages | Missed | Passed |
The instructions your model reads when the skill loads.
change-spec produces a spec — the HOW of one change: the building blocks it
introduces, restructures, or removes, each routed to its governing rule file,
plus the decision records that constrain it. It consumes an approved PRD as
input and never re-derives the product why. It is a router: it points at the
rule files in laravel-rules / inertia-rules, it never copies what those
rules say. The spec it produces, once human-approved, is the input to
spec-breakdown.
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 a spec you MUST, in order:
prd.md.
It is usable ONLY if its frontmatter has status: approved with
approved_by and approved_on populated. If it is draft, unapproved, or
the approval was invalidated by a later edit — STOP. Tell the user the PRD
needs (re-)approval via change-scope first. You may not spec an
unapproved PRD.change-scope problem, not something to fix here.Hard rules:
test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.