Requirements Quality Reviewer
Review business requirements for completeness, clarity, consistency, risks, assumptions and readiness for delivery.
Act as a Senior Business Analyst, Product Owner and Requirements Engineering specialist.
Review the following requirements specification.
Requirements:
{{requirements}}
Business Context:
{{business_context}}
Known Constraints:
{{constraints}}
Stakeholders:
{{stakeholders}}
Evaluate the requirements across the following dimensions:
1. Completeness
2. Clarity
3. Consistency
4. Business Value
5. Scope Definition
6. Testability
7. Feasibility
8. Traceability
9. Data Requirements
10. Security Requirements
11. Non-Functional Requirements
12. Compliance Considerations
13. Dependencies
14. Risks
15. Assumptions
16. Edge Cases
17. Stakeholder Alignment
18. Delivery Readiness
For each dimension provide:
- Assessment
- Findings
- Risks
- Missing Information
- Recommendations
Identify:
- Ambiguous requirements
- Missing business rules
- Missing validation rules
- Missing user scenarios
- Missing non-functional requirements
- Hidden assumptions
- Conflicting requirements
- Duplicate requirements
- Untestable requirements
- Requirements that should be split
Classify every issue as:
- Low
- Medium
- High
Create:
1. Executive Summary
2. Quality Assessment Table
3. Requirement Gaps
4. Assumptions Register
5. Risk Register
6. Clarification Questions
7. Recommendations
8. Requirements Readiness Assessment
Assign one overall readiness status:
- Ready for Analysis
- Ready for Refinement
- Ready for Development
- Requires Clarification
- Requires Discovery
- Blocked
Do not invent requirements.
Clearly separate:
- Confirmed Information
- Assumptions
- Risks
- Recommendations
Return a structured review suitable for Business Analysis, Product Management and Jira refinement activities.Works with ChatGPT, Claude, Gemini and Copilot.
Example in action
See how this prompt transforms a real input into a structured result.
Requirements: Customers must be able to reset forgotten passwords. The system should send a reset link by email. The user should be able to choose a new password. Business Context: The organization wants to reduce customer-service requests related to account access. Known Constraints: The solution must comply with existing security policies. Stakeholders: - Product Owner - Security Team - Customer Support
EXECUTIVE SUMMARY Overall Readiness Status: Requires Clarification Quality Score: 7/10 -------------------------------------------------- QUALITY ASSESSMENT Completeness: Medium Finding: Core user flow is described. Missing Information: - Reset link expiration - Password policy - Rate limiting - Handling of unknown email addresses -------------------------------------------------- RISKS High: Account enumeration may be possible if different messages are shown for existing and non-existing accounts. Medium: No audit requirements are defined. -------------------------------------------------- ASSUMPTIONS 1. Email addresses are already verified. 2. Existing authentication services support password updates. 3. Security policies allow email-based recovery. -------------------------------------------------- MISSING REQUIREMENTS - Link expiration period - Password complexity validation - Reset token lifecycle - Failed-attempt handling - Accessibility considerations - Logging and monitoring requirements -------------------------------------------------- CLARIFICATION QUESTIONS 1. How long should a reset link remain valid? 2. Is multi-factor verification required? 3. What should happen after repeated reset requests? 4. Are audit logs required for compliance purposes? -------------------------------------------------- RECOMMENDATION Do not proceed to development until security and validation requirements are confirmed.