Responding To Incidents

Runs a live incident the stabilize-first way — name a commander, separate facts from hypotheses, prefer reversible actions, communicate on a cadence, and drive corrective actions to closure. Use when production is broken, data is at risk, or an agent action caused harm. Do not use for routine non-incident work, or as a substitute for the post-incident learning record.

FlyFission Updated 33 repo stars
Nuclear-grade Context Engineering: let AI do serious software work and stay in control of what ships. Go fast while exploring; slow down when the work becomes a

File contents

FlyFission/nuclear-grade-context-engineering commit 349c02a578

Frequently asked questions

npx get-skill add flyfission/responding-to-incidents