Bug Report Analyzer

You are a product manager analyzing bug reports. Triage and prioritize this bug.

**Bug Report:**
{bug_description}

**Reporter:** {reporter_name}
**Impact:** {impact_description}
**Frequency:** {frequency}

Analyze and triage:

**1. Bug Classification:**

**Severity:**
- **Critical (P0):** System down, data loss, security vulnerability
- **High (P1):** Major feature broken, affects many users, no workaround
- **Medium (P2):** Feature partially broken, has workaround, affects some users
- **Low (P3):** Minor issue, cosmetic, edge case, affects few users

**Assigned Severity:** {severity}
**Rationale:** {severity_justification}

**2. Impact Assessment:**

**User Impact:**
- Affected users: {user_count} ({percentage}% of active users)
- User segments affected: {segments}
- Workaround available: {yes/no}
- User complaints received: {complaint_count}

**Business Impact:**
- Revenue impact: {revenue_impact}
- Churn risk: {churn_risk}
- SLA breach: {sla_status}
- PR/brand risk: {brand_risk}

**Technical Impact:**
- Systems affected: {systems}
- Data integrity: {data_status}
- Performance degradation: {performance_impact}

**3. Root Cause Analysis (5 Whys):**

**Problem:** {problem_statement}

**Why 1:** Why did this happen?
Answer: {answer_1}

**Why 2:** Why did {answer_1} occur?
Answer: {answer_2}

**Why 3:** Why did {answer_2} occur?
Answer: {answer_3}

**Why 4:** Why did {answer_3} occur?
Answer: {answer_4}

**Why 5:** Why did {answer_4} occur?
Answer: {answer_5} (Root cause)

**Root Cause:** {root_cause}

**4. Reproduction Steps:**

**Can Reproduce:** {yes/no}

**Steps to Reproduce:**
1. {step_1}
2. {step_2}
3. {step_3}

**Expected Behavior:** {expected}
**Actual Behavior:** {actual}

**Environment:**
- Version: {version}
- Platform: {platform}
- Browser: {browser}
- Device: {device}

**5. Immediate Actions:**

**Hotfix Required:** {yes/no}

**Immediate Actions (< 24 hours):**
- [ ] {action_1}
- [ ] {action_2}
- [ ] {action_3}

**Communication:**
- Notify affected users: {yes/no}
- Message: "{user_message}"
- Status page update: {yes/no}

**6. Fix Plan:**

**Estimated Time to Fix:** {time_estimate}

**Development Plan:**
1. **Investigation:** {investigation_steps}
   - Time: {investigation_time}
2. **Fix Development:** {fix_approach}
   - Time: {dev_time}
3. **Testing:** {test_plan}
   - Time: {test_time}
4. **Deployment:** {deployment_plan}
   - Time: {deployment_time}

**Dependencies:** {dependencies}
**Risks:** {risks}

**7. Prevention:**

**Similar Bugs Possible:** {yes/no}

**Prevention Measures:**
- Code review improvements: {review_changes}
- Testing additions: {test_additions}
- Monitoring additions: {monitoring_additions}
- Documentation updates: {doc_updates}

**8. Bug Report Quality Assessment:**

**Current Report Quality:** {quality_score}/10

**Missing Information:**
- [ ] Reproduction steps
- [ ] Expected vs actual behavior
- [ ] Environment details
- [ ] Screenshots/logs
- [ ] Impact assessment

**Improved Bug Report Template:**
```
**Title:** [Clear, specific title]

**Severity:** {severity}

**Description:**
[What happened? Be specific]

**Steps to Reproduce:**
1. {step}
2. {step}
3. {step}

**Expected Behavior:**
[What should happen?]

**Actual Behavior:**
[What actually happened?]

**Impact:**
- Users affected: {number}
- Workaround: {yes/no}
- Frequency: {how_often}

**Environment:**
- Version: {version}
- Platform: {platform}
- Browser: {browser}

**Screenshots/Logs:**
[Attach relevant files]

**Business Impact:**
[Why does this matter?]
```

**9. Stakeholder Communication:**

**Engineering Team:**
"[Critical/High/Medium/Low] Bug: {title}

Impact: {user_count} users affected
Severity: {severity}
Priority: {priority}

Root Cause: {root_cause}

Action Required: {action}
Timeline: {timeline}

Details: [Ticket link]"

**Customer Support:**
"Aware of bug: {title}

**Status:** Under investigation / Fix in progress / Fixed
**ETA:** {eta}

**Workaround (if available):**
{workaround_steps}

**Messaging for customers:**
'{customer_message}'

Will update when fix is deployed."

**10. Post-Mortem (after fix):**

**Incident Summary:**
- Date/Time: {datetime}
- Duration: {duration}
- Users affected: {user_count}
- Root cause: {root_cause}

**Timeline:**
- {time}: Bug reported
- {time}: Investigation began
- {time}: Root cause identified
- {time}: Fix deployed
- {time}: Verified resolved

**What Went Well:**
- {positive_1}
- {positive_2}

**What Went Wrong:**
- {negative_1}
- {negative_2}

**Action Items:**
- [ ] {action_item_1} - Owner: {owner} - Due: {date}
- [ ] {action_item_2} - Owner: {owner} - Due: {date}

Provide: Triage assessment + fix plan + communication plan + post-mortem.