Product Requirements Analysis and Gap Identifier

You are a product analyst who reviews requirements for completeness and clarity. Analyze these product requirements.

[PASTE PRODUCT REQUIREMENTS DOCUMENT OR SPECIFICATIONS]

Context:
- Product: [PRODUCT NAME]
- Requirement source: [STAKEHOLDER / CUSTOMER / INTERNAL]
- Development phase: [CONCEPT / DESIGN / BUILD]
- Team: [WHO WILL BUILD]

Provide:

**Requirements Overview**
- Total requirements: X
- By category: [breakdown]
- Priority distribution:
- Clarity score: X/10

**Requirements Quality Assessment**

| Quality Criteria | Score | Issues |
|-----------------|-------|--------|
| Clarity | /5 | |
| Measurability | /5 | |
| Achievability | /5 | |
| Relevance | /5 | |
| Time-bound | /5 | |
| Testability | /5 | |

**Requirements Analysis**

For each requirement or section:

| ID | Requirement | Type | Priority | Status | Concerns |
|----|-------------|------|----------|--------|----------|
| R1 | [text] | Functional | Must | Unclear | Vague scope |

**Gaps Identified**

**Missing Requirements**
- [Area] - No requirements for [function]
- [Area] - Missing edge case handling

**Unclear Requirements**
| Req ID | Issue | Clarification Needed |
|--------|-------|---------------------|
| R3 | Ambiguous | What does "fast" mean? |

**Conflicting Requirements**
- R5 and R12 conflict because...

**Untestable Requirements**
- R7: "System should be easy to use" - How to measure?
- Suggested rewrite: [specific, measurable version]

**Questions for Stakeholders**
1. [Question about unclear requirement]
2. [Question about missing information]
3. [Question about priority]

**Assumptions Made**
| Assumption | Risk if Wrong |
|------------|---------------|
| | |

**Dependencies Identified**
- R3 depends on R1
- External dependencies: [list]

**Recommended Rewrites**

Original: "[Original requirement]"
Recommended: "[SMART requirement version]"

**Effort Estimation Considerations**
- High complexity requirements
- Unknown areas requiring research
- Integration points

**Sign-off Checklist**
- [ ] All stakeholders reviewed
- [ ] Conflicts resolved
- [ ] Gaps filled
- [ ] Acceptance criteria defined
- [ ] Dependencies documented

You are a product analyst who reviews requirements for completeness and clarity. Analyze these product requirements.

[PASTE PRODUCT REQUIREMENTS DOCUMENT OR SPECIFICATIONS]

Context:
- Product: [PRODUCT NAME]
- Requirement source: [STAKEHOLDER / CUSTOMER / INTERNAL]
- Development phase: [CONCEPT / DESIGN / BUILD]
- Team: [WHO WILL BUILD]

Provide:

**Requirements Overview**
- Total requirements: X
- By category: [breakdown]
- Priority distribution:
- Clarity score: X/10

**Requirements Quality Assessment**

| Quality Criteria | Score | Issues |
|-----------------|-------|--------|
| Clarity | /5 | |
| Measurability | /5 | |
| Achievability | /5 | |
| Relevance | /5 | |
| Time-bound | /5 | |
| Testability | /5 | |

**Requirements Analysis**

For each requirement or section:

| ID | Requirement | Type | Priority | Status | Concerns |
|----|-------------|------|----------|--------|----------|
| R1 | [text] | Functional | Must | Unclear | Vague scope |

**Gaps Identified**

**Missing Requirements**
- [Area] - No requirements for [function]
- [Area] - Missing edge case handling

**Unclear Requirements**
| Req ID | Issue | Clarification Needed |
|--------|-------|---------------------|
| R3 | Ambiguous | What does "fast" mean? |

**Conflicting Requirements**
- R5 and R12 conflict because...

**Untestable Requirements**
- R7: "System should be easy to use" - How to measure?
- Suggested rewrite: [specific, measurable version]

**Questions for Stakeholders**
1. [Question about unclear requirement]
2. [Question about missing information]
3. [Question about priority]

**Assumptions Made**
| Assumption | Risk if Wrong |
|------------|---------------|
| | |

**Dependencies Identified**
- R3 depends on R1
- External dependencies: [list]

**Recommended Rewrites**

Original: "[Original requirement]"
Recommended: "[SMART requirement version]"

**Effort Estimation Considerations**
- High complexity requirements
- Unknown areas requiring research
- Integration points

**Sign-off Checklist**
- [ ] All stakeholders reviewed
- [ ] Conflicts resolved
- [ ] Gaps filled
- [ ] Acceptance criteria defined
- [ ] Dependencies documented