Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evolution-foundation/pm-write-spec
Write a feature spec or PRD from a problem statement or feature idea.
Passed 16 of 22 test cases with the skill, and 9 of 22 without it.
and 6 more in the full report
7 fixed9 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We've noticed a significant drop-off during user onboarding on our web application. Can you generate a complete feature spec to tackle this onboarding friction? The document should include a problem summary, measurable outcomes and explicit out-of-scope items, user stories in standard format, categorized requirements with acceptance criteria, leading and lagging success metrics, unresolved questions, and timeline dependencies.
| Checked | Without skill | With skill |
|---|---|---|
| Engages the user with questions to gather context on user problems or business constraints before producing the specification | Missed | Passed |
| Avoids immediately outputting the full generated specification document | Missed | Passed |
The instructions your model reads when the skill loads.
Write a feature specification or product requirements document (PRD).
/pm-write-spec $ARGUMENTS
Ask the user what they want to spec. Accept any of:
Ask the user for the following. Be conversational — do not dump all questions at once. Ask the most important ones first and fill in gaps as you go:
If Linear MCP (int-linear-review) is available:
If Notion MCP is available:
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.