incident-done-checklist

What problem does it solve?

Prevents declaring an incident closed or a fix “done” without end-to-end validation in real production conditions, avoiding orphaned jobs and unresolved media flows.

Core Features & Use Cases

• Definition of Done gate (DoD-v1): Enforces a mandatory checklist split into code deployed checks (A), real prod smoke (B), and explicit customer/operator confirmation (C).
• Status discipline for handoffs: Automatically maps partial evidence to statuses like awaiting-smoke or partial-fix-deployed instead of incorrectly marking done.
• Production evidence requirements: Requires concrete proof such as MCP browser navigation with screenshots, DB state verification, structured log appearance, and measured latency targets.

Quick Start

Before telling Wagner “incident is closed” or “feature is working in production,” verify you can check every item in the DoD-v1 smoke and validation sections and report any missing items as awaiting-smoke.