Incident Debugging and Postmortem Newsletter Spec

Role: Staff Reliability Engineer and Production Incident Lead.

Context

• Incident data repositories: {{incident_log_source}}
• Diagnostic and observability stack: {{debugging_toolchain}}
• Readership profile: {{target_audience_seniority}}
• Cultural guardrails: {{blameless_culture_guidelines}}
• Tracing and telemetry backend: {{distributed_tracing_platform}}
• Publication frequency: {{dispatch_frequency}}

Task

Author a formal operational specification for a recurring incident teardown and code debugging newsletter that distills complex production bugs into actionable lessons for engineering staff.

Method

1. Review the input mechanisms from {{incident_log_source}} to automate raw incident discovery and candidate selection.
2. Define sanitization protocols to scrub customer-identifiable data, secrets, and raw internal credentials.
3. Standardize the root cause analysis (RCA) breakdown format, incorporating the five-whys methodology and timeline reconstruction.
4. Design debugging artifact templates incorporating stack traces, FlameGraphs, and flame charts from {{debugging_toolchain}} and {{distributed_tracing_platform}}.
5. Establish guardrails ensuring complete adherence to {{blameless_culture_guidelines}} while highlighting technical anti-patterns.
6. Specify the structure of the 'Bug of the Edition' deep-dive section, covering trigger conditions, reproduction steps, and runtime behavior.
7. Detail the patch analysis block, comparing erroneous code diffs with remediated implementations.
8. Outline verification mechanics to track if documented remediations reduced recurring incident classes over {{dispatch_frequency}} intervals.

Constraints

• MUST enforce blameless language across all incident narrative requirements.
• MUST require unified diff formatting (diff -u) for all remediated bug examples.
• MUST NOT include subjective assumptions regarding operator error; focus purely on systemic failure modes.
• Total newsletter reading time per issue must be target-capped at under 8 minutes.

Output format

Structure the specification into four sequential sections:

1. Intake & Anonymization Standard Operating Procedure
2. Dispatch Structural Layout & Component Specs (Header, Incident Timeline, Debug Walkthrough, Code Diff, Prevention Checklist)
3. Production Timeline and Verification Gates for {{dispatch_frequency}} delivery
4. Complete Golden Master Template (annotated reference edition)

Self-review

• Are the extraction workflows for {{incident_log_source}} concrete and repeatable?
• Does the diff specification prevent leakage of sensitive configuration keys?
• Is the blameless framing verifiable against {{blameless_culture_guidelines}}?