| name | product-requirements |
| title | product-requirements |
| version | 1.0.0 |
| type | skill |
| description | Concise 1-page PRD template: problem, scope, functional/non-functional requirements, edge cases, acceptance criteria, risks, rollout strategy, and success metrics. |
| author | Hermes Agent |
| tags | ["prd","product","requirements","template","documentation"] |
product-requirements — PRD Template v1.0.0
1. Problem
What specific problem or opportunity are we solving? What evidence supports this?
2. Scope — In
Which features, capabilities, or changes are explicitly included in this work?
3. Scope — Out
What is explicitly not in scope to prevent scope creep?
4. Functional Requirements
Key functional behaviours the solution must implement. Bulleted, each testable.
5. Non-Functional Requirements
Performance, security, scalability, availability, maintainability constraints.
6. Edge Cases
Off-nominal inputs, error states, concurrent access, boundary conditions to handle.
7. Acceptance Criteria
Concrete pass/fail conditions that define "done" for this work.
8. Risks & Mitigations
Top 2–3 risks with potential impact and planned mitigations.
9. Rollout Strategy
How the change reaches users — feature flag, staged rollout, dark launch, etc.
10. Success Metrics
Quantitative signals (KPIs, counters, SLIs) used to decide if the change is working.
11. Dependencies
External teams, upstream services, third-party libraries, or prerequisite work required.
12. Open Questions
Decisions yet to be made; list the decision-maker and deadline for each.
13. Timeline
Brief milestone cadence — kickoff, design review, implementation, QA, release target.
14. Appendix / References (optional)
Links to related docs, designs, research, or prior art.
