product-prd
/product-prd — Product Requirements Document
Write structured PRDs that define what to build and why. PRDs are product-focused — they describe the problem, users, and requirements without prescribing technical implementation.
When to Use
- User says "write a PRD", "product requirements", "feature spec"
- After a brainstorm session, to formalize requirements
- When a feature idea needs to be documented before building
Process
Step 1: Gather Context
Check for existing artifacts:
docs/brainstorms/— Use brainstorm output as starting point- User-provided description or
$ARGUMENTS - If neither exists, ask clarifying questions
More from elliottrjacobs/bench-skills
product-tech-spec
Write technical specifications bridging product requirements and implementation. Use when the user says "tech spec", "technical spec", "architecture doc", "system design", or after writing a PRD and before planning implementation.
11product-naming
Expert naming process for products, companies, and features based on David Placek's methodology. Use when the user says "name this", "brainstorm names", "naming process", or needs to find a name for a product, feature, company, or project.
10knowledge-compound
Document solutions, decisions, and learnings into a searchable knowledge base. Use when the user says "document this", "compound this", "save this solution", "capture this", or after completing significant work that uncovered reusable knowledge.
8security-audit
Deep security audit of codebase with parallel domain-focused agents. Use when the user says "security audit", "check for vulnerabilities", "security review", or before a launch/deployment. More thorough than the security reviewer in /engineer-review.
8engineer-review
Comprehensive multi-agent code review with parallel specialist reviewers. Use when the user says "review this", "code review", "review my PR", provides a PR number or branch, or after completing a /engineer-work cycle.
8product-brainstorm
Guided requirements exploration through structured dialogue. Use when the user says "brainstorm", "explore this idea", "help me think through", or when requirements are fuzzy and need clarification before writing specs.
8