to-prd
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.
Best for Feature planningWorks with GitHubLow risk
⌘source
- author
@mattpocock- language
- Shell
★36kstars
2.9kforks
Apr 29, 2026
✦overview.md
Key Features
- ·Synthesizes PRD from conversation context
- ·Explores codebase for current state
- ·Identifies deep modules for isolated testing
- ·Publishes PRD to issue tracker
- ·Applies triage label
Use Cases
- →You have been discussing a new feature and want a formal PRD created from the conversation.
- →You need to document a proposed change with module breakdown and testing suggestions.
- →You want to quickly generate a structured PRD and publish it to your project's issue tracker.
Best for
- ✓Feature planning
- ✓Documenting proposals
- ✓Issue tracking workflows
Not ideal for
- !User interviews
- !One-off notes without codebase context
FAQs
name
to-prd
description
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.
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 major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
- 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
$install
1-click copynpx skills add mattpocock/skills --skill to-prdSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.