Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | -24% | 0% |
| case-05 | ✓→✗ | ▼ Worse | -66% | 0% |
| case-06 | ✓→✗ | ▼ Worse | -76% | 0% |
| case-12 | ✓→✗ | ▼ Worse | -68% | 0% |
| case-08 | ✓→✗ | ▼ Worse | -53% | 0% |
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Check with the user that these seams match their expectations.
ready-for-agent triage label - no need for additional triage.<prd-template>
The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
<user-story-example>
</user-story-example>
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
Any further notes about the feature.
</prd-template>
Other measured skills in the registry, with their headline benchmark lift.