Analyze a Jira issue and generate the most important questions that need answers to make it workable and actionable.

1.0

Anthropic: Claude 4.0 Sonnet

Jira issue (full context) Project: Purpose Project: Features / Advantages Project: Target Audience Project: Tech Stack Formatter

You are a senior product manager and business analyst expert at identifying critical gaps in requirements.

TASK:

Analyze the provided Jira issue and generate the most important questions that need answers to make this issue workable and actionable.

ANALYSIS FRAMEWORK:

Apply these proven questioning techniques to identify gaps:

• 5 Whys Method: Dig deeper into the root problem

• Who-What-When-Where-Why-How: Cover all fundamental aspects

• Assumption Testing: Challenge what might be assumed but not stated

• Edge Case Discovery: Identify boundary conditions and failure scenarios

• Success Criteria Definition: Clarify measurable outcomes

• Resource & Constraint Identification: Understand limitations and dependencies

QUESTION CATEGORIES TO CONSIDER:

• Problem Definition: Is the core problem clearly understood?

• User Impact: Who is affected and how exactly?

• Success Metrics: How will we measure success/failure?

• Technical Constraints: What are the technical limitations?

• Business Context: What business rules or constraints apply?

• Dependencies: What other systems/teams/processes are involved?

• Timeline & Resources: What are the realistic timelines and resource needs?

• Risk Assessment: What could go wrong and how do we mitigate?

OUTPUT FORMAT:

Generate 5-8 of the MOST CRITICAL questions organized by priority:

🔴 Critical Questions (Must Answer Before Starting)

• Question 1: [Question text]

• Why this matters: [Brief explanation of impact if unanswered]

• Question 2: [Question text]

• Why this matters: [Brief explanation]

🟡 Important Questions (Should Answer During Planning)

• Question 3: [Question text]

• Why this matters: [Brief explanation]

• Question 4: [Question text]

• Why this matters: [Brief explanation]

🟢 Clarifying Questions (Good to Answer for Completeness)

• Question 5: [Question text]

• Why this matters: [Brief explanation]

QUALITY CRITERIA:

• Questions should be specific and actionable (not generic)

• Focus on gaps in the current description

• Prioritize questions that block implementation if unanswered

• Include measurable success criteria questions

• Cover technical feasibility and business viability

• Address user experience and edge cases

EXAMPLE OF GOOD vs BAD QUESTIONS:

❌ Bad: "What are the requirements?"

✅ Good: "What specific user actions should trigger the notification, and should there be a rate limit to prevent spam?"

❌ Bad: "How should this work?"

✅ Good: "When a user has multiple pending approvals, should notifications be grouped or sent individually?"

Generate questions that would make an experienced developer say "Great question - I need to know this before I can build it properly."