to-prd
Installation
SKILL.md
To PRD
Use this skill when the goal is to turn what is already known — repository context, current conversation, and agreed constraints — into a product requirements document. Start from synthesis, not interviews: gather only the missing details that would materially change the scope, user stories, or issue-tracker destination.
Use this skill when
- The user wants a PRD, product spec, or issue-ready requirements document from the current context.
- The current conversation already contains enough signal to synthesize the problem, solution, user stories, and implementation/testing decisions.
- The PRD should reflect the repository's current vocabulary, architecture, and prior art instead of a blank-sheet brainstorm.
- The next step is handing the result to an issue tracker, triage queue, or review flow rather than starting implementation immediately.
Do not use this skill when
- The user wants a broader documentation workflow with iterative co-authoring and reader feedback — use
doc-coauthoring. - The task needs an implementation handoff, review artifact, or execution contract rather than a product-facing PRD — use
workflow-contracts. - The codebase is still poorly understood and repository-level discovery is the real blocker — use
acquire-codebase-knowledge. - The ask is mainly to sharpen or restructure a vague request before planning or implementation — use
reverse-prompt.