responding-to-incidents
CommunityStabilize incidents with clear ownership.
Software Engineering#timeline#learning#incident#decision-record#corrective-actions#stabilize-first#facts-vs-hypotheses
AuthorFlyFission
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Incidents are destabilizing events; this skill provides a disciplined, commander-led approach to stabilize first, separate facts from hypotheses, document decisions, and drive corrective actions to closure.
Core Features & Use Cases
- Stabilize-first workflow: prioritize reversible actions and a single commander to guide response.
- Evidence-led timeline: maintain a living record separating facts from hypotheses for auditability.
- Action ownership and handoff: capture owned corrective actions and a clean handoff to learning and deficiency records.
Quick Start
Initiate an incident by naming a commander, recording initial symptoms, and listing immediate reversible actions to implement.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: responding-to-incidents Download link: https://github.com/FlyFission/nuclear-grade-context-engineering/archive/main.zip#responding-to-incidents Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.