prd
Installation
Summary
Generate comprehensive Product Requirements Documents that translate business vision into technical specifications.
- Follows a strict three-phase workflow: discovery interview to fill knowledge gaps, analysis and scoping to identify dependencies, and technical drafting using a standardized PRD schema
- Requires concrete, measurable success criteria and acceptance criteria; explicitly avoids vague language like "fast" or "intuitive" in favor of quantifiable benchmarks
- Covers executive summary, user personas and stories, technical architecture, AI system requirements with evaluation strategies, and phased rollout planning with risk analysis
- Includes discovery questions on core problems, success metrics, and constraints before generating any document; presents drafts for iterative feedback on specific sections
SKILL.md
Product Requirements Document (PRD)
Overview
Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.
When to Use
Use this skill when:
- Starting a new product or feature development cycle
- Translating a vague idea into a concrete technical specification
- Defining requirements for AI-powered features
- Stakeholders need a unified "source of truth" for project scope
- User asks to "write a PRD", "document requirements", or "plan a feature"