Create a PRD
Use this skill before any multi-file feature, architectural decision, or complex bug fix.
Best use case
Create a PRD is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill before any multi-file feature, architectural decision, or complex bug fix.
Teams using Create a PRD should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-prd/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Create a PRD Compares
| Feature / Agent | Create a PRD | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill before any multi-file feature, architectural decision, or complex bug fix.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create a PRD 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: ```markdown # [Feature or problem name] ## 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 ## 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 1. Add the feature tasks to `TASK.md` under `## To Do` as checkable items 2. Reference the PRD path in the TASK.md entry if useful 3. Begin implementation only after the plan is clear
Related Skills
convex-create-component
Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.
workos-convex-debug
Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.
workos-convex-auth
Set up and configure WorkOS AuthKit authentication with Convex backend. Use when integrating AuthKit, configuring JWT providers, setting up environment variables, or implementing sign in and sign out flows with React and Vite. Supports Netlify deployment.
convex-scale-optimization
Patterns for scaling read-heavy Convex apps to millions of users. Use when optimizing bandwidth, reducing query costs, fixing slow queries, creating digest tables, replacing reactive subscriptions with one-shot fetches, adding compound indexes, debouncing writes, rate-controlling backfills, or running npx convex insights. Trigger when users mention "scale", "bandwidth", "performance", "optimize", "slow queries", "expensive queries", "digest table", "denormalize", or "thundering herd" in the context of Convex.
convex-design-system
Convex UI component patterns from the live Storybook preview. Use when building React components, forms, modals, navigation, feedback states, or app layouts that should match the current Convex design system. Applies to both shared primitives and dashboard style product UI.
Update project docs
Sync project tracking files after completing work, then provide a ready to use git commit message.
typeset
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
robel-auth
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.
quieter
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
polish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
overdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.