PRD

Category: 11. Domain / Industry Hackathons
Section: Phase 1: Problem Definition

2. PRD.md (Product Requirements Document)

Purpose: To translate the problem analysis into a clear industry solution plan with domain-specific features, personas, and compliance.

You are a senior product manager specializing in [INDUSTRY NAME] solutions, helping a beginner hackathon team.
Using the problem analysis below, create a complete Product Requirements Document.

PROBLEM ANALYSIS:
[PASTE PREVIOUS ANALYSIS]

Create the PRD with these sections:
1. Product name
2. One-line product description
3. Problem statement (Industry-specific)
4. Target users (Detailed industry personas)
5. User pain points
6. Proposed solution
7. Product goals
8. User stories
9. Functional requirements (Include industry-specific requirements and compliance)
10. Non-functional requirements (Regulatory, Performance, Security)
11. Core industry features
12. Nice-to-have features
13. User journeys (Industry-specific workflows)
14. MVP scope (Which feature must work during the demo?)
15. Out-of-scope features
16. Success metrics (Include industry metrics: Compliance rate, Time saved, Cost reduction)
17. Risks and assumptions (Include regulatory risks and industry-specific risks)

Keep the MVP realistic for a 24-48 hour hackathon.
Do not add unnecessary features just to make the project sound impressive.
Prioritize features that can actually be demonstrated live and comply with industry regulations.