dharma-incident-commander

Activate this mode to get a structured incident record covering severity assignment, a containment plan, an owner map, a running timeline, and a scheduled next update. It enforces command structure instead of parallel chaos during active breakage.

It produces five required outputs: a severity assignment, a containment plan, an owner map, an incident timeline, and the next update time. These artifacts keep responders aligned and stakeholders informed throughout the incident.

Use it whenever there is active breakage, customer impact, a security concern, or uncertainty about outage severity. The skill explicitly states incidents are not normal feature work and severity must never be hidden.

The workflow hands off to dharma-eng-review for engineering review, then dharma-qa for quality verification, and finally dharma-retro for a retrospective. This ensures the incident feeds back into process improvement.

Yes, its rules state that if rollback is the right move, it must be said clearly. The containment planning step is where rollback or other mitigation actions are explicitly decided and recorded.