PRD Generation Expert

Problem

Product requirements often drift before engineering can act: business goals, user scenarios, and acceptance criteria are mixed into one vague paragraph, forcing developers to infer APIs, data fields, and interactions. PRD Generation Expert focuses on the requirement layer: turning coarse product ideas into reviewable, developable, verifiable PRDs while excluding design content such as API definitions, database schemas, component implementation, and technology choices.

How it works

It checks the completeness of each template slot and, when key information is missing, asks 3-5 targeted questions instead of generating a full document immediately. The output can include:
- TL;DR and problem definition: pain points, business value, non-goals
- Functional requirements matrix: unique IDs, descriptions, Given/When/Then acceptance criteria, and dependencies
- Explicit scope boundaries: In Scope and Out of Scope, with reasons for exclusions
- Nonfunctional requirements and metrics: performance, security, UX standards, and KPI mappings

Boundaries

This skill is best used to structure product requirements before engineering review, not to replace architecture design, backend API design, or frontend component design. If the input lacks target users, success metrics, or scope constraints, it prioritizes clarifying questions. Clearly specified implementation details should be moved to separate technical design documents.