write-a-prd
Installation
SKILL.md
Purpose
Structured interview -> PRD specifying what to build from the user's perspective. Pipeline: plan-feature -> write-a-prd -> review-prd -> glossary -> (design-ux) -> design-feature -> review-plan.
Starting
Before asking anything:
- Look for a scope document in
./plans/(*-scope.md). If found, read it fully — problem statement, stakeholders, feasibility, and scope are your starting context. - Explore the codebase for the product perspective — existing user flows, UI patterns, terminology, conventions.
- Search for existing documentation — user guides, help docs, product specs, onboarding flows.
If scope doc exists, ground your first question in it: "I've read the scope for [feature]. The problem is [X], stakeholders are [Y], scope includes [Z]. First question: [question about target users]."
No scope doc? Start from the user's description, beginning with problem/motivation.
Interview Protocol
Product discovery interview. Focus on user needs, behaviors, and success criteria — not technical implementation.