From workflow-toolkit
This skill should be used when the user asks to "write a PRD", "create a product requirements document", "plan a new feature", "write requirements", "draft a spec", "spec out a feature", "define requirements", or wants to plan and define what to build before building it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-toolkit:write-a-prd*.md*.txtThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a Product Requirements Document through structured user interview, codebase exploration, and module design. Submit the final PRD as a GitHub issue, or write it as a markdown file if no repository is available or the user prefers.
Create a Product Requirements Document through structured user interview, codebase exploration, and module design. Submit the final PRD as a GitHub issue, or write it as a markdown file if no repository is available or the user prefers.
Steps may be skipped if clearly unnecessary for the scope of the work.
Ask the user for a thorough description of:
Let the user talk. Do not interrupt with questions yet — the goal is to get the full picture before digging in.
Verify the user's assertions and understand the current state:
Report findings to the user before proceeding.
Interview the user relentlessly about every aspect of the plan until reaching shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.
For each question, provide a recommended answer. If a question can be answered by exploring the codebase, explore the codebase instead of asking.
Cover at minimum:
Sketch out the major modules to build or modify. Actively look for opportunities to extract deep modules — modules that encapsulate significant functionality behind a simple, testable interface that rarely changes.
A deep module (as opposed to a shallow module) provides:
Present the module sketch to the user. Confirm:
Once there is complete understanding of the problem and solution, write the PRD using the template in references/prd-template.md.
gh issue createOnce the PRD is submitted, suggest: "When ready to break this into implementation tickets, ask me to convert the PRD to issues."
references/prd-template.md — PRD template with all required sectionsnpx claudepluginhub pau-vega/ai-devkitGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.