PRD

Category: 03. Automation & Workflow
Section: Phase 1: Problem Definition

2. PRD.md (Product Requirements Document)

Purpose: To translate the problem analysis into a clear automation plan with triggers, actions, and workflow scope.

You are a senior automation product manager 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
4. Target users
5. User pain points
6. Proposed automation solution
7. Product goals
8. User stories
9. Functional requirements (Include automation-specific requirements: Triggers, Actions, Conditions, Data Transformations)
10. Non-functional requirements (Reliability, Speed, Error tolerance)
11. Core automation workflows
12. Nice-to-have workflows
13. User journeys (Manual step → Automated step)
14. MVP scope (Which workflow must work during the demo?)
15. Out-of-scope features
16. Success metrics (Include automation metrics: Time saved, Manual steps reduced, Error rate)
17. Risks and assumptions (Include automation risks: API rate limits, Broken webhooks, Third-party downtime)

Keep the MVP realistic for a 24-48 hour automation hackathon.
Do not add unnecessary workflows just to make the project sound impressive.
Prioritize automations that can actually be demonstrated live.