engineering / Plan & design
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Put it to work.
Ask your agent to use to-prd, or let it load the skill when your task matches the description.
Use the to-prd skillInvocation syntax varies by agent. Use the skill name in your prompt, or your agent’s supported slash command.
About this skill
Turn the current conversation context into a Product Requirements Document and publish it to the project issue tracker. No interview — synthesizes from what's already been discussed.
Flow
flowchart LR
E[Explore repo] --> M[Sketch modules<br/>look for deep modules]
M --> U{User confirms<br/>modules + tests}
U --> W[Write PRD]
W --> P[Publish with<br/>needs-triage label]Install
npx skills@latest add smeltery/skillsPRD template
The skill emits a fixed-section PRD: Problem Statement, Solution, User Stories (numbered, actor-benefit), Implementation Decisions, Testing Decisions, Out of Scope, Further Notes.
Caveat
Like /to-issues, this skill expects an issue tracker and triage label
vocabulary configured upstream. Hand-configure or install the upstream
setup-matt-pocock-skills skill before invoking.
Files
SKILL.md— canonical skill definition.
Attribution
Ported from mattpocock/skills under MIT. See THIRD_PARTY_LICENSES.md.
Read the full SKILL.md
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.
Process
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can.
Check with the user that these seams match their expectations.
- Write the PRD using the template below, then publish it to the project issue tracker. Apply the
needs-triagetriage label so it enters the normal triage flow.
Problem Statement
The problem that the user is facing, from the user's perspective.
Solution
The solution to the problem, from the user's perspective.
User Stories
A LONG, numbered list of user stories. Each user story should be in the format of:
- As an , I want a , so that
This list of user stories should be extremely extensive and cover all aspects of the feature.
Implementation Decisions
A list of implementation decisions that were made. This can include:
- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
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.
Testing Decisions
A list of testing decisions that were made. Include:
- A description of what makes a good test (only test external behavior, not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)
Out of Scope
A description of the things that are out of scope for this PRD.
Further Notes
Any further notes about the feature.