Workflow
Bug Fix

# Bug Fix

Turn a reported bug into a clear diagnosis, a scoped fix approach, practical validation steps, and a confident ship or rollback path.

## Audience

Engineering, product, support, and operator teams responsible for resolving product or system bugs quickly and safely.

## Best For

Production bugs, customer-reported issues, regressions, flaky behavior, and defects that need diagnosis, prioritization, and a practical fix path.

## Contexts

### Support Specialist

Clarify the reported issue, impact, urgency, and the exact behavior that is failing.

Handoff: Start from the bug report itself, what is breaking for the user, and what evidence is already available.

### Product Manager

Decide the severity, scope the response, and frame the smallest credible fix worth shipping first.

Handoff: Turn the issue into a clear fix goal, tradeoff call, and delivery recommendation.

### Software Engineer

Diagnose the likely technical cause and outline the implementation path for the fix.

Handoff: Describe the root cause hypothesis, fix shape, risks, and what needs to change in code or systems.

### QA Engineer

Define the checks, evidence, and measurements that confirm the bug is fixed and not regressing elsewhere.

Handoff: Recommend the smallest useful validation plan so the team can ship with confidence.

## 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.

## 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.

## Follow Up

Implement the fix, validate it against the release criteria above, and call out any remaining risks or regressions.