PRD Generator

A PRD is the contract between what the client asked for and what the team will build. This skill turns a requirement brief into a PRD that a developer could pick up and start estimating against — no back-and-forth needed.

Instructions

Step 1: Take the requirement brief as input

Ideally this is the JSON brief from the requirement-analyzer skill. If the user hands you raw requirements instead, run the extraction mentally first, then proceed.

Step 2: Write the Project Vision

One short paragraph. It states who the product is for, the core value, and the outcome that makes the project a success. This is the anchor for every scope decision that follows.

Step 3: Fill the PRD template

Use the exact structure in assets/prd-template.md. Fill every section. Where the brief is silent, write "To be confirmed" and add the item to Open Questions rather than inventing detail.

Step 4: Make scope decisions explicit

The single most valuable part of a PRD is the Out of Scope section. For a new project, state plainly what this release will not include. Ambiguity here is what causes scope creep and estimate blowout later.

Step 5: Run the quality gate

Before finalizing, check the PRD against references/prd-quality-checklist.md. Do not hand off a PRD that fails the gate.

Output structure

ALWAYS follow this order (full template in assets/prd-template.md):

# [Project Name] — Product Requirements Document
## Project Vision
## Objectives and Success Metrics
## Personas
## Scope (In Scope)
## Out of Scope
## Functional Requirements
## Non-Functional Requirements
## Dependencies and Integrations
## Risks
## Open Questions

Example

Given a brief for a pharmacy reorder app, the Project Vision reads:

"For pharmacy customers who repeatedly refill the same prescriptions, this mobile app removes the trip to the store: customers reorder in two taps and choose a delivery window, so refilling a prescription takes minutes instead of a half-day errand."

The Objectives section then turns that into measurable targets (for example, "median reorder time under 3 minutes"), and Out of Scope explicitly excludes new-prescription intake and insurance claims for this release.

Troubleshooting

• PRD is vague. Usually the input brief was thin. Return to requirement-analyzer output and resolve open questions before writing more.
• PRD is bloated with features nobody asked for. Cut anything not traceable to a goal or functional requirement in the brief. Every PRD line should trace back to the requirement that justifies it.