write-prd
Write PRD
Create a new Product Requirements Document in the project's PRD directory.
Step 1: Find the PRD Directory and Next Number
Look for an existing PRD directory in the project. Common locations: docs/prds/, prds/, docs/prd/, prd/. If none exists, ask the user where PRDs should live.
List existing PRD files and determine the next sequence number. Files follow the pattern NNNN-slug.md (e.g., 0019-user-onboarding.md). The next file would be 0020-<slug>.md. If no PRDs exist yet, start at 0001.
Step 2: Mini-Discovery Workshop
Before writing, run a structured discovery pass. There are four areas to cover:
- Problem & users — Who struggles today, and what breaks for them?
- Business value — What metric, revenue, or cost does this affect?
- Constraints — Tech stack, platform, timeline, must-nots?
- Risks — What's most likely to make this fail or get stuck?
More from queso/ai-team-skills
v0-setup
Fetches v0.dev designs via the Platform API and prepares them for adaptation into your project. Handles folder setup, source code retrieval, component inventory, and produces an adaptation brief. Use when integrating v0 designs.
12start-new-app
Scaffolds a new app from the context-kit template. Clones the repo, renames the project, initializes git, creates a PRD directory, and asks the user to provide a PRD.
8address-pr-feedback
Fetches PR review comments, categorizes each as Will Fix / Won't Fix / New Issue, addresses fixable feedback using TDD, commits, pushes, and posts a summary.
7code-review
Reviews all unmerged code in the current branch for readability, security, correctness, types, and test quality. Produces a summary of issues to fix before merging.
1