# Atlas Incident Brief

> Turn incident notes into an evidence-based brief with impact, timeline, causes, and follow-up actions.

- Skill: `deer-flow/atlas-incident-brief` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add deer-flow/atlas-incident-brief`
- Raw SKILL.md: https://api.skillmd.com/api/skills/deer-flow/atlas-incident-brief/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: deer-flow (https://skillmd.com/u/deer-flow)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/deer-flow/atlas-incident-brief

---


# Atlas incident brief

Use this Skill when the user supplies incident notes, a timeline, or a set of
observations that need to become a clear incident brief.

1. Read [`references/template.md`](references/template.md).
2. Preserve timestamps and distinguish facts from hypotheses.
3. State user impact before internal implementation details.
4. Do not assign a root cause unless the evidence supports it.
5. Give every follow-up action an owner or explicitly mark it unassigned.

If essential evidence is absent, list the smallest set of questions needed to
complete the brief.