Incident Ops sample

Bug Report to Root Cause Brief

Packages bug descriptions, logs, and reproduction notes into a concise root-cause brief for PMs, engineering leads, QA, and support operations.

Why this sample matters

Bug Report to Root Cause Brief sample

Convert bug evidence into a root-cause brief with severity, impact framing, fix direction, and prevention steps.

Review checklist

- Check whether the section structure matches the operating artifact your team expects.
- Review how owners, decisions, risks, and next actions are separated instead of blended together.
- Use the raw markdown download if you want to compare the preview against the underlying source file.

Sample preview

The likely cause is a duplicate invoice-create event emitted during retry before idempotency state is fully committed.

High - customer-facing financial duplication with operational impact.

Enforce idempotency before the retry path can emit a second invoice-create event.

Billing engineering lead