to-prd
mattpocock/skills · Agent Skill
Turns a conversation into a PRD and publishes it to the issue tracker.
Jump to install ↓Overview
| Publisher |  mattpocockCommunity |
|---|---|
| Repository | mattpocock/skills ↗ |
| Skill folder | to-spec |
| Stars | 303,928 |
| Forks | 25,577 |
| Bundled files | 2 |
| License | MIT |
| Last updated | October 22, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “to-prd” skill from mozgi.io (https://mozgi.io/skills/mattpocock-to-prd/) for me. 1. Download the archive: https://mozgi.io/skills/mattpocock-to-prd/download If it fails, take the skill folder from the source: https://github.com/mattpocock/skills/tree/main/skills/engineering/to-spec 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “to-prd” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/to-prd/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .claude/skills cp -r /tmp/skills/skills/engineering/to-spec .claude/skills/to-spec
Restart Claude Code — the skill appears in the list; call it manually with /to-prd. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .agents/skills cp -r /tmp/skills/skills/engineering/to-spec .agents/skills/to-spec
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $to-prd. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .cursor/skills cp -r /tmp/skills/skills/engineering/to-spec .cursor/skills/to-spec
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills mkdir -p .gemini/skills cp -r /tmp/skills/skills/engineering/to-spec .gemini/skills/to-spec
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyThis skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
Process
1. 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 spec, and respect any ADRs in the area you're touching.
2. 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. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
3. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.
<spec-template>
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:
1. As an <actor>, I want a <feature>, so that <benefit>
<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>
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 spec.
Further Notes
Any further notes about the feature.
</spec-template>
Frequently asked questions
What does the to-prd skill do?
Turns a conversation into a PRD and publishes it to the issue tracker.
How do I install to-prd?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with to-prd?
Skills are plain Markdown instructions (the Agent Skills format), so to-prd works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is to-prd free?
The skill is published openly by mattpocock under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.
Related skills
All skills →tdd
Red-green-refactor workflow for building features and fixes one slice at a time.
mattpocock304k
diagnosing-bugs
Systematic bug diagnosis through reproduce, minimize, hypothesize, instrument, and fix.
mattpocock304k
domain-modeling
Builds and sharpens project domain models and terminology.
mattpocock304k
ask-matt
Router that picks the right Matt Pocock engineering flow for the current task.
mattpocock304k
next-cache-components
Enable Cache Components in a Next.js app and resolve blocking routes surfaced during adoption.
vercel143k
migrate-radix-to-base
Migrate React projects and shadcn components from Radix UI to Base UI, handling route objects, consumer props, and progressive wrapper migration.
shadcn-ui127k