Score
9.2
/ 10
Installs
364K
Repo Stars
215.5K
Last Updated
5d ago
Quality Ratio
95%
Description
Verified
Language
Shell
First Published
Apr 2026
Summary
The To Prd agent skill transforms the current conversation context and codebase understanding into a structured Product Requirements Document (PRD), which is then published to the project's issue tracker. This agent skill is ideal for product managers, technical leads, and developers who need to quickly formalize product requirements from existing discussions or architectural decisions into a detailed plan. It is a skill with 250K installs, indicating significant adoption among teams. The skill instructs the agent to synthesize information without interviewing the user, exploring the repo to understand the codebase, and adhering to project glossaries and Architectural Decision Records. It guides the agent to sketch major modules, identify deep modules for isolation, and then construct a PRD following a template that includes Problem Statement, Solution, extensive User Stories, Implementation Decisions, Testing Decisions, and Out of Scope sections. After drafting, it publishes the PRD to the issue tracker with a `needs-triage` label. Note that the skill relies on pre-configured issue tracker and triage label vocabulary, requiring an initial setup command if not already provided.
Skill Definition
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
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.
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.