create-prd skill
✓ VerifiedGenerates a Product Requirements Document in markdown format to define scope and plan complex technical changes before implementation.
- GitHub stars
- 404
- Files
- 5
- Last commit
- Nov 9, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the create-prd skill do?
create-prd generates a Product Requirements Document in markdown format to define scope and plan complex technical changes before implementation.
Summary generated from the skill's SKILL.md.
About the create-prd skill
Planning complex technical changes by generating markdown documentation is what this skill enables for developers. It creates a scope contract for non-trivial work such as multi-file features, schema modifications, or architectural decisions. When an agent loads this tool, it produces a structured markdown file in the prds/ directory using a kebab-case slug, ensuring every major change has a documented problem statement, proposed solution, and list of files to change.
Users trigger the process by requesting a PRD or using specific commands. The tool relies on system time for UTC metadata and follows a strict template including edge cases and verification steps. Once the document is written, the skill automatically queues the work by adding checkable items to task.md. This prevents developers from starting implementation until the plan is clear and the scope is defined, making it a reliable way to manage migrations or deep bug investigations.
What an agent can do with it
- 1Documenting multi-file feature implementationsAsk the agent to write a PRD before starting a feature that requires changing three or more files.
- 2Planning database schema migrationsRequest a plan for a change that involves modifying the existing data model or schema.
- 3Managing technical task queuesAutomatically add new development tasks to your project tracking file after defining the scope.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the create-prd skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the create-prd skill in Plugin
/plugin marketplace add waynesutton/builder-skills /plugin install builder-skills@waynesutton
Install the create-prd skill in Claude Code
~/.claude/skills/create-prd/SKILL.md
$ npx degit waynesutton/builder-skills/skills/create-prd ~/.claude/skills/create-prdInstall the create-prd skill in Claude Code (project)
.claude/skills/create-prd/SKILL.md
$ npx degit waynesutton/builder-skills/skills/create-prd .claude/skills/create-prdInstall the create-prd skill in Codex
~/.agents/skills/create-prd/SKILL.md
$ npx degit waynesutton/builder-skills/skills/create-prd ~/.agents/skills/create-prdInstall the create-prd skill in Gemini CLI
~/.gemini/skills/create-prd/SKILL.md
$ npx degit waynesutton/builder-skills/skills/create-prd ~/.gemini/skills/create-prdInstall the create-prd skill in Claude.ai
npx degit waynesutton/builder-skills/skills/create-prd create-prd && zip -r create-prd.zip create-prd # claude.ai → Customize → Skills → + → Create skill → Upload a skill → create-prd.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablewaynesutton/builder-skills/skills/create-prd is public and reachablegithub.com/waynesutton/builder-skills/tree/HEAD/skills/creat ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/waynesutton/builder-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/waynesutton/builder-skills/blob/HEAD/skills/creat ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/waynesutton/builder-skills/blob/HEAD/skills/creat ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 77 linesgithub.com/waynesutton/builder-skills/blob/HEAD/skills/creat ↗Pass
SKILL.md
View on GitHubCreate a PRD
A PRD is the scope contract for one change. Write it before the code, keep it under two screens, and update it when the plan changes.
Activate with @create-prd, /create-prd, or "write a PRD".
When to write one
- Three or more files will change
- The schema changes
- An architectural choice is being made (auth, hosting, data model)
- A bug took real investigation to diagnose
- The work will be referenced later as a migration guide or how-to
When to skip it
- A single file fix that is obvious from logs or types
- A typo, a CSS tweak, or a label change
- A copy change to markdown content
Location and naming
- Every PRD lives in
prds/. - File name:
prds/<feature-or-problem-slug>.md, kebab case. Example:prds/adding-email-auth.md. - Always
.md, never.prd. - Finished or sensitive PRDs move to
prds/archive/.
Template
Copy the full template from references/prd-template.md. The required parts:
# <Feature or problem, sentence case>
Created: YYYY-MM-DD HH:mm UTC
Last Updated: YYYY-MM-DD HH:mm UTC
Status: Draft | In Progress | Done
## Problem
## Root cause (bugs only)
## Proposed solution
## Files to change
## Edge cases
## Verification steps
## Out of scope
## Task completion log
Get the time from the system (date -u +"%Y-%m-%d %H:%M UTC"). Never invent it.
Filling it in
- Problem before solution. If the problem section is thin, the solution is a guess.
- For bugs, name the root cause: the line, query, or design choice. If it is unknown, say so and list the two likeliest candidates.
- Files to change is the scope. If a file not on the list needs to change, update the PRD first.
- Edge cases save the next session. Write down anything non obvious you found.
- Each verification step has an expected result, so someone else could run it.
- Out of scope is where extra ideas wait. Link an issue or a new PRD if they should happen later.
- The completion log is append only.
After writing it
- Add the tasks to
task.mdunder## To Doas checkable items, with the PRD path. - Share the PRD with the user if it has a real choice in it. Wait for an answer on that choice.
- Start building only once the plan is clear. Update
Last UpdatedandStatusas it moves.
Never
- Write a PRD for a one line change.
- Pad it. Two screens is plenty for most work.
- Mark it Done before its verification steps ran.
Files in this skill
5create-prd skill questions
How do I install the create-prd skill in Claude Code?
Run npx degit waynesutton/builder-skills/skills/create-prd ~/.claude/skills/create-prd. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the create-prd skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Where are the PRD files stored and how are they named?
PRDs are stored in the prds/ directory using kebab-case filenames with a .md extension.