PRD Generator

Generate comprehensive Product Requirements Documents from validated idea files.

Input

Requires project folder path in $ARGUMENTS containing:

• idea.md – Product concept and technical context (required)
• validate.md – Evaluation and recommendations (required)

If path not provided, ask user for the project folder location.

Workflow

Phase 1: Validate Input

1. Check $ARGUMENTS/idea.md exists
2. Check $ARGUMENTS/validate.md exists
3. If prd.md exists, create backup: prd.backup.YYYYMMDD_HHMMSS.md

Phase 2: Extract Context

From idea.md:

• Product name/concept
• Target audience
• Goals & objectives
• Technical context (stack, constraints)

From validate.md:

• Verdict and ratings
• Strengths/weaknesses
• Competitors
• Enhanced version suggestions
• Implementation roadmap

Phase 3: Clarify Requirements

Ask user (if not clear from input files):

• Official product name?
• Business model? (SaaS, marketplace, freemium)
• Target MVP timeframe?
• Team size/composition?
• Compliance requirements? (GDPR, HIPAA, SOC2)

Phase 4: Generate PRD

Create prd.md with these sections:

1. Product Overview – Vision, users, objectives, success metrics
2. User Personas – 2-3 detailed personas from target audience
3. Feature Requirements – Matrix with MoSCoW prioritization, user stories, acceptance criteria
4. User Flows – Primary flows with mermaid diagrams
5. Non-Functional Requirements – Performance, security, compatibility, accessibility
6. Technical Specifications – Architecture diagram, frontend/backend/infrastructure specs
7. Analytics & Monitoring – Key metrics, events, dashboards, alerts
8. Release Planning – MVP and version roadmap with checklists
9. Open Questions & Risks – Questions, assumptions, risk mitigation
10. Appendix – Competitive analysis, glossary, revision history

See references/prd-template.md for full template structure.

Phase 5: Output

1. Write prd.md to project folder
2. Summarize sections created
3. Highlight areas needing user review
4. Suggest next steps

Modification Mode

If user wants to modify existing PRD:

1. Create timestamped backup
2. Ask what to modify (features, priorities, timeline, specs, personas)
3. Apply changes preserving structure
4. Update revision history

Guidelines

• Thorough: Cover all sections comprehensively
• Realistic: Base on validate.md feasibility ratings
• Specific: Include concrete metrics and criteria
• Actionable: Every section guides implementation
• Visual: Include mermaid diagrams for architecture and flows