I have initial product requirements for {{feature}}. Help me identify ambiguities and ask clarifying questions. Initial requirements: {{requirements}} Analyze these requirements through multiple lenses: FUNCTIONAL CLARITY - What behaviors are underspecified? - What edge cases are missing? - What "obvious" assumptions need stating? USER CLARITY - Who exactly is the user? - What is their context when using this? - What are their success criteria? TECHNICAL CLARITY - What technical constraints are unstated? - What integrations are assumed? - What performance expectations exist? BUSINESS CLARITY - What business metrics should improve? - What is out of scope explicitly? - What dependencies exist? For each ambiguity found, provide: 1. The ambiguous statement 2. Why it is ambiguous 3. 2-3 clarifying questions to ask 4. Suggested default if no answer received Prioritize by risk of misinterpretation.
Product Requirements Clarification
Identify and resolve ambiguities in product requirements
43 copies0 forks
Details
Category
AnalysisUse Cases
Clarify requirementsReduce specification riskImprove requirement quality
Works Best With
gpt-4claude-3
Created Updated Shared