Use this skill before any multi-file feature, architectural decision, or complex bug fix.
Activate with: @create-prd
Location and naming
All PRDs live in prds/ folder
File name: prds/<feature-or-problem-slug>.md
Extension is always .md, not .prd
Use kebab-case for the filename (e.g., prds/adding-email-auth.md)
Template
Copy and fill in this template:
# [Feature or problem name]
Created: YYYY-MM-DD HH:mm UTC
Last Updated: YYYY-MM-DD HH:mm UTC
Status: Draft | In Progress | Done
## Summary
1-2 sentence description of what this is and why it matters.
## Problem
What is broken or missing. Include symptoms, error messages, or user-facing impact.
## Root cause (for bugs)
What actually caused it. Do not skip this for bugs.
## Proposed solution
How to fix or build it. Be specific about the approach chosen and why.
## Files to change
- `path/to/file.ts` - what changes and why
- `convex/schema.ts` - if schema changes are needed
## Edge cases and gotchas
Anything non-obvious that came up during analysis. This section saves the next session.
## Verification
How to confirm the fix or feature works:
- [ ] Step 1
- [ ] Step 2
## Task completion log
- [ ] Task name completed (YYYY-MM-DD HH:mm UTC)
## Related
Links to related PRDs, issues, or external docs if any.
When to create a PRD
3+ files will change
Schema changes are involved
Architectural decisions are being made (auth, hosting, data model)
A bug required significant investigation to diagnose
A feature needs to be referenced later as a migration guide or implementation reference
When to skip a PRD
Single file bug fix obvious from logs or types
Typo, CSS tweak, or label change
Copy change to markdown content
After creating the PRD
Add the feature tasks to TASK.md under ## To Do as checkable items
Reference the PRD path in the TASK.md entry if useful
Keep Last Updated current as tasks move forward
Begin implementation only after the plan is clear
1---2name: create-prd3description: Create a PRD4---5# Create a PRD67Use this skill before any multi-file feature, architectural decision, or complex bug fix.89Activate with: `@create-prd`1011## Location and naming1213- All PRDs live in `prds/` folder14- File name: `prds/<feature-or-problem-slug>.md`15- Extension is always `.md`, not `.prd`16- Use kebab-case for the filename (e.g., `prds/adding-email-auth.md`)1718## Template1920Copy and fill in this template:2122```markdown23# [Feature or problem name]2425Created: YYYY-MM-DD HH:mm UTC26Last Updated: YYYY-MM-DD HH:mm UTC27Status: Draft | In Progress | Done2829## Summary30311-2 sentence description of what this is and why it matters.3233## Problem3435What is broken or missing. Include symptoms, error messages, or user-facing impact.3637## Root cause (for bugs)3839What actually caused it. Do not skip this for bugs.4041## Proposed solution4243How to fix or build it. Be specific about the approach chosen and why.4445## Files to change4647- `path/to/file.ts` - what changes and why48- `convex/schema.ts` - if schema changes are needed4950## Edge cases and gotchas5152Anything non-obvious that came up during analysis. This section saves the next session.5354## Verification5556How to confirm the fix or feature works:5758- [ ] Step 159- [ ] Step 26061## Task completion log6263- [ ] Task name completed (YYYY-MM-DD HH:mm UTC)6465## Related6667Links to related PRDs, issues, or external docs if any.68```6970## When to create a PRD7172- 3+ files will change73- Schema changes are involved74- Architectural decisions are being made (auth, hosting, data model)75- A bug required significant investigation to diagnose76- A feature needs to be referenced later as a migration guide or implementation reference7778## When to skip a PRD7980- Single file bug fix obvious from logs or types81- Typo, CSS tweak, or label change82- Copy change to markdown content8384## After creating the PRD85861. Add the feature tasks to `TASK.md` under `## To Do` as checkable items872. Reference the PRD path in the TASK.md entry if useful883. Keep `Last Updated` current as tasks move forward894. Begin implementation only after the plan is clear
Run npx skillmds@latest add get-convex/create-prd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Create a PRD It is listed under Product & Planning on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
get-convex (@get-convex) published this skill. Their other Agent Skills are listed on their SkillMD profile.
get-convex