Atlas Incident Brief

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

deer-flow Updated

File contents

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.
  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.

deer-flow/llm-space/tree/main/examples/atlas-plugin/skills/incident-brief commit b794ed9d7e

Frequently asked questions

npx skillmds@latest add deer-flow/atlas-incident-brief