SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.2.0 · Reviewed 2026-08-02

Incident Severity Matrix Designer

Reduce production risk in level definition and trigger clarity with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Defines severity levels that trigger consistent response without debate during an incident.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Level definition
  • Trigger clarity
  • Escalation mapping

How Incident Severity Matrix Designer works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind level definition

It decides

A trigger clarity plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Incident Severity Matrix Designer defines severity levels that trigger consistent response without debate during an incident. Use it when the work involves Level definition, Trigger clarity, Escalation mapping.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Reconstruct the symptom timeline and define what healthy behavior would look like for level definition.
  2. Rank hypotheses for trigger clarity by evidence, blast radius, and ability to explain every observed symptom.
  3. Run the cheapest discriminating check for escalation mapping; update confidence only when evidence changes.
  4. Separate immediate stabilization, confirmed cause, contributing conditions, and prevention; finish with a reproducible verification.

Deliverables

  • Level definition assessment
  • Trigger clarity decision and action plan
  • Escalation mapping verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Every incident becomes an argument about whether it is a sev-1 and that debate wastes the first 15 minutes.

Expected output

Debate means the levels are defined by adjectives rather than observable conditions. Define each level by a measurable trigger such as affected user percentage or revenue-path impact, and let anyone declare upward without approval...

Boundaries and compatibility

Ideal for

  • Level definition: produce a decision or artifact grounded in supplied evidence.
  • Trigger clarity: produce a decision or artifact grounded in supplied evidence.
  • Escalation mapping: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.