Incident follow-through
Turn the postmortem actions into shipped changes: the test, the timeout, the alert, the guardrail.
Every incident ends with a list that names the test which would have caught it, the missing timeout, the alert nobody wrote, and the guardrail that would have held.
The team agrees on that list, then the next incident arrives first. Here each item becomes a real change, linked to the incident.
Add the test that would have caught it
The test fails against the commit that caused the incident
Turn the incident timeline into the runbook for the next one
Each step verified against the real dashboards and commands
Add the alert that would have paged sooner
Rule and runbook in the same pull request
Add the guardrail the postmortem asked for
The guardrail refuses the exact input that caused the incident
Add the missing timeout, retry budget, or breaker
Failure-path tests at the boundary, defaults documented
Close the observability gap the incident exposed
The question nobody could answer at 3am is now answerable
Make the manual recovery step a script with a dry run
Dry-run output attached, the real execution stays with the team
Put the agent team to work on your backlog
Connect a repository and assign SHIP your first issue. Your first missions are free.