Turns a raw product or feature idea into an approved PRD — the product WHY of one change to a capability.
SkillScore95Maintained
Automatic
◆Product Management pack
Last verified 8/3/2026
What it changes
Passed 20 of 21 test cases with the skill, and 6 of 21 without it.
Without skill27%
With skill95%
Checks it passed that the model alone missed
The PRD frontmatter leaves approved_by empty.
The response declines to generate a PRD document.
The PRD frontmatter sets change to 0001-dark-mode.
and 23 more in the full report
15 fixed6 passed either way1 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+33%
Agent turns
0%
Response time
-64%
Model gemini-3.6-flashMeasured 8/3/2026v121 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md160 linessingle file
Change Scope
What this skill does
change-scope produces a PRD — the WHY of one change to a capability: the
problem, the user's current pain, the product value, user stories, and scope.
It runs BEFORE any technical spec. It owns the product reasoning and makes no
technical decisions. The PRD it produces is the required input to
change-spec, and change-spec will refuse a PRD that a human has not
approved.
Where the state tree lives
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), and
product/vision.md means {declared-root}/product/vision.md.
STOP — how this skill works
Before producing a PRD you MUST, in order:
CLASSIFY the idea. State the classification and the reasoning out loud:
New capability — the product has no existing area for this.
Change to an existing capability — name the capability. Make this call
ONLY after reading that capability's existing PRDs and decision records
(see Precedence); prior decisions are often what make a change
architectural.
In-shape work — a small modification needing no PRD and no spec. Say so
and STOP: direct the work to the relevant rules skill's code gate. Do not
manufacture a PRD for a one-line change.
RESOLVE THE CAPABILITY ANCHOR.
The capability already exists → the PRD will cite its README.md.
The capability does NOT exist → create a provisional capability stub
(see "Creating a provisional capability stub") so the PRD has a real
parent to cite. The stub is an anchor, not a capability description.
ALLOCATE THE CHANGE NUMBER (see "Numbering a change").
WRITE THE PRD (see "What a PRD must contain").
SEEK HUMAN APPROVAL (see "Approval"). Until a human approves, the PRD is not