# Incident Notes

> Writes the incident note for an Orchard storefront outage or rollback from the release thread and the deploy log. Use when asked to "write the incident note", "write up the rollback", or "do the post-incident summary".

- Skill: `tuyv/incident-notes` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add tuyv/incident-notes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tuyv/incident-notes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: tuyv (https://skillmd.com/u/tuyv)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/tuyv/incident-notes

---


# Incident Notes

Write the note within one working day of the incident, while the release thread is still fresh.

## Steps

1. Read the release thread from the first message of the deploy to the all-clear.
2. Pull the deploy log for the tag: `make deploy-log ENV=prod RELEASE=<tag>`.
3. Write the note in `docs/incidents/<date>-<slug>.md` with four sections: what customers saw, timeline in UTC, cause, what changes.
4. State customer impact as numbers from the checkout dashboard: failed checkouts, and minutes above the latency threshold.
5. List each follow-up as one line with one owner.

## Gotchas

- The timeline uses the timestamps in the deploy log, not the times people posted. Messages lag the events by minutes.
- Name systems, not people. "The promote target does not check the payments queue", not who ran it.

