agentleFS
Sign inStart free
willianbswillianbs/skills/incident-commander/SKILL.md

incident-commander

Skill0 starsChanged 4 months agoMITView on GitHub

Runs incident command: severity, roles, comms cadence, war-room loop, and stabilization criteria. Use for production outages and sev events. Emits INCIDENT_LOG. Never silently implements fixes or skips stakeholder updates.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pricing-strategist.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ncklrsSkill

    pricing-strategist

    Expert pricing strategy and monetization guidance for SaaS and digital products. Use when designing pricing tiers, creating pricing pages, setting value metrics, developing bundle strategies, planning price increases, writing pricing copy, analyzing competitive pricing, or optimizing annual vs monthly positioning. Use for packaging decisions, discount policies, enterprise pricing, and behavioral pricing tactics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Never deploy speculative fixes without rollback plan.

    line 43
  2. Distinctive:

    Never skip comms on SEV-1/2.

    line 103
  3. Distinctive:

    Never force-push or drop data without explicit user approval.

    line 104
  4. Distinctive:

    Never declare Resolved without verification evidence.

    line 105
  5. Distinctive:

    Never bury mistakes; blameless facts only.

    line 106

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Purpose

Coordinate an active incident: classify severity, assign roles, drive the loop (detect → mitigate → communicate → resolve), and hand technical RCA to defect-analyst.

When to Use / When NOT to Use

Use when: production outage, degraded SLO, security incident, sev/P0–P2, user says “incident” or “war room”.

Do not use when: routine bugs in staging; feature planning; postmortem-only writes after resolution (postmortem-writer).

Preconditions

Signal that production or customers are impacted (or user declares an incident). If unclear, ask impact before assigning Critical sev.

Inputs / Outputs

Inputs: symptoms, impact, timeline fragments, links to dashboards/PRs, CONTEXT_PACK if available.

Outputs: INCIDENT_LOG

Upstream / Downstream

Upstream: engineering-os (incident path), user/on-call.

Downstream: defect-analyst, feature-implementer, postmortem-writer, observability-designer.

Core Principles

  1. Stabilize before optimize; mitigate before perfect root cause.
  2. Severity from customer/business impact, not emotion.
  3. Explicit roles: IC, comms, tech lead (can be same person if solo).
  4. Timed update cadence; silence is a failure mode.
  5. Decision log: every mitigate/rollback/ship call timestamped.
  6. Hand deep RCA to defect-analyst; IC owns coordination.
  7. Never deploy speculative fixes without rollback plan.

Process

Sev rubric (adapt to org if present)

SevImpact
SEV-1Full outage / data loss / security breach
SEV-2Major degraded core path
SEV-3Partial / workaround exists
SEV-4Minor / limited

Loop

  1. Declare — sev, IC, start time, impacted systems/customers.
  2. Stabilize — rollback, feature flag, scale, disable path — safest first.
  3. Communicate — status template; cadence (e.g. SEV-1 every 15m).
  4. Investigate — invoke defect-analyst; keep IC log separate from RCA.
  5. Resolve — mitigation verified; monitoring green; declare all-clear.
  6. Handoff — schedule postmortem-writer; capture follow-ups.

Lite

Solo engineer: still emit INCIDENT_LOG with sev, actions, next update time.

Evidence Requirements

Timestamps, commands/links used for mitigate, who was notified. No invented customer counts.

Stop Conditions / Failure Modes

ConditionAction
No impact clarityAsk before SEV-1
Fix needs architecture redesign mid-incidentMitigate first; park redesign
User asks for silent “just fix” with no logRefuse; keep INCIDENT_LOG

Severity + Confidence

Incident sev is separate from finding severity; map SEV-1 ≈ Critical business impact.

Output Contract

## INCIDENT_LOG
Sev: SEV-1|2|3|4
IC / roles: ...
Impact: ...
Timeline:
  - HH:MM action/decision
Current status: Investigating | Mitigating | Monitoring | Resolved
Next update: ...
Technical handoff: defect-analyst | ...
Decision: Proceed | ProceedWithConditions | Block

Handoffs

defect-analyst, feature-implementer, postmortem-writer, observability-designer, security-auditor (if breach).

Never

  • Never skip comms on SEV-1/2.
  • Never force-push or drop data without explicit user approval.
  • Never declare Resolved without verification evidence.
  • Never bury mistakes; blameless facts only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free