Product Requirements Generator (Spec → Build)

Turn product ideas into clear specifications that engineering can build without constant clarification meetings.

Prompt
Create a product specification for: {FEATURE}

PROBLEM STATEMENT
What problem does this solve? {PROBLEM}
For whom? {USERS}
Why is it urgent? {URGENCY}

BUSINESS GOALS
Success means: {SUCCESS_METRIC}
This will increase: {IMPACT}
Timeline: {TIMELINE}

THE FEATURE: {FEATURE}

COMPLETE SPECIFICATION:

OVERVIEW
[1 sentence what this is]

GOALS FOR THIS FEATURE
- Goal 1: [Specific, measurable]
- Goal 2: [Specific, measurable]
- Goal 3: [Specific, measurable]

USER PERSONAS & FLOWS
[For each main user type:]

Persona: {PERSONA}
Pain point: [What they struggle with]

User flow: "{PERSONA}"
[Step 1: User does X]
[Step 2: System shows Y]
[Step 3: User takes action Z]
[Step 4: Outcome/success state]

FEATURE BREAKDOWN
[Specific components/functionality]

Component 1: {DESCRIPTION}
- What it does
- Where it appears
- How users interact with it

Component 2: {DESCRIPTION}
[Continue...]

EDGE CASES & ERROR HANDLING
- If [condition], then [system does]
- Error: [What could go wrong] → [Recovery]
- Edge case: [Unusual but possible scenario] → [How handled]

TECHNICAL REQUIREMENTS
Platform: {PLATFORM}
Technology constraints: {CONSTRAINTS}
Integration needs: {INTEGRATIONS}
Performance needs: {PERFORMANCE}

ACCEPTANCE CRITERIA
The feature is done when:
- [ ] User can [action 1]
- [ ] System shows [outcome 1]
- [ ] [Edge case] is handled correctly
- [ ] Performance is [metric]
- [ ] All error states show helpful messages
- [ ] [Integration] works end-to-end

DEPENDENCIES
- Does this depend on [X]? Timeline: [when]
- Does [Y] depend on this? Timeline: [when]

Feature: {FEATURE}
Users: {USERS}
Variations
Format as user stories (As a [user], I want [feature], so [benefit]).
Add technical architecture diagram.
Include data model changes required.
Create a phased rollout plan.
Works well with
GPT
Claude