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.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/to-prd/SKILL.mdThis skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know. (If the requirements are not settled yet, that is /grill-me or /grill-with-docs, not this.)
AGENTS.md or constitution/local-workflow.md names it. If neither does, ask once and then record the answer there rather than in this file.ready-for-agent label — its presence means an agent may take the work solo, its absence means a human stays in the loop. There is no literal HITL label; absence is the signal.Explore the repo to understand the current state of the codebase, if you haven't already. Use docs/domain-glossary.md vocabulary throughout the PRD, and respect the decision records in docs/adr/ that cover 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.
ready-for-agent label if the work is mechanical with a checkable definition of done — no additional triage needed.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:
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.
A PRD that spans more than one context window goes through /to-tickets before any code is written (shared invariant §1). One that fits a single window can go straight to /implement.
Adapted from engineering/to-prd in mattpocock/skills — MIT, see .claude/skills/LICENSE-mattpocock-skills.md. Upstream expects a separate setup skill to have supplied the tracker and label vocabulary; here that vocabulary is the kit's own autonomy-label mechanism.
agranado2k/google-books-clojure
76766c5
Also appears in
since Nov 19, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.