Bug Fix
OiDetails
Description
Turn a reported bug into a clear diagnosis, a scoped fix approach, practical validation steps, and a confident ship or rollback path.
Constraints
Prioritize the safest fix that resolves the bug clearly. Respect production risk, known constraints, regression risk, and any customer-facing urgency already in play.
Experiments
Offer plausible fix options, rollout choices, or diagnostic checks when they materially improve confidence, speed, or risk reduction.
Measurement
Measure whether the bug is reproduced clearly, the proposed fix addresses the root issue, and regressions or unresolved edge cases are surfaced before shipping.
Definition of done
Done means the team has a clear bug diagnosis, a practical fix plan, validation steps, and an obvious next action to ship or safely test the fix.
Post Execution Follow Up
Implement the fix, validate it against the release criteria above, and call out any remaining risks or regressions.
Steps
Handoff note
Start from the bug report itself, what is breaking for the user, and what evidence is already available.
Handoff note
Turn the issue into a clear fix goal, tradeoff call, and delivery recommendation.
Handoff note
Describe the root cause hypothesis, fix shape, risks, and what needs to change in code or systems.
Handoff note
Recommend the smallest useful validation plan so the team can ship with confidence.
Guardrails
Require confirmation before continuing with unusually long compiled prompts.
Metadata
Example use cases
Review this bug report and tell me the most likely cause, safest fix, and how we should validate it before shipping.
Take this regression and turn it into a concrete diagnosis, implementation plan, and release checklist.
Categories
Tags
Connections