Writes a short PRD in prds/<slug>.md before non trivial work: problem, root cause for bugs, proposed solution, files to change, edge cases, verification steps, and a completion log, with UTC metadata. Then queues the work in task.md. Use before any multi file feature, schema change, architectural decision, or bug that took real investigation, or when the user says write a PRD, @create-prd, or plan this.
95%
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
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".
prds/.prds/<feature-or-problem-slug>.md, kebab case. Example: prds/adding-email-auth.md..md, never .prd.prds/archive/.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 logGet the time from the system (date -u +"%Y-%m-%d %H:%M UTC"). Never invent it.
task.md under ## To Do as checkable items, with the PRD path.Last Updated and Status as it moves.waynesutton/convexskills
853b196
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.