Post-incident collaboration handoff checklist
Use this checklist to validate Teams and GitHub handoff quality after runtime remediation.
Preconditions
- Incident has a confirmed status (
resolved,partial, orescalated). - Root cause statement is documented.
- Remediation actions include rollback notes.
Teams milestones
- Investigation started update posted.
- Root cause and remediation identified update posted.
- Incident resolved (or escalated) update posted.
- Channel and timestamp captured in incident record.
GitHub durable follow-up
- Issue created with incident ID, impact summary, root cause, and remediation summary.
- Evidence links added (metrics, logs, timeline, runbook notes).
- Source-of-truth drift risk described (runtime patch vs repo state).
- Recommended code change path documented (manifest/IaC/service config).
PR handoff readiness
- Draft PR request payload prepared (branch target, files likely to change, acceptance checks).
- Human review ownership assigned.
- No merge automation enabled without explicit policy approval.
Completion criteria
- Teams and GitHub artifacts exist and are linked in incident history.
- Follow-up work is assigned and visible in engineering workflow.