SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.2.0 · Reviewed 2026-08-02

Incident Review Facilitator

Reduce production risk in facilitation structure and blameless framing with evidence, explicit trade-offs, and a verification plan.

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

Facilitates blameless reviews that surface systemic causes instead of settling on human error.

₹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

  • Facilitation structure
  • Blameless framing
  • Systemic cause surfacing

How Incident Review Facilitator works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind facilitation structure

It decides

A blameless framing plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Incident Review Facilitator facilitates blameless reviews that surface systemic causes instead of settling on human error. Use it when the work involves Facilitation structure, Blameless framing, Systemic cause surfacing.

  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 facilitation structure.
  2. Rank hypotheses for blameless framing by evidence, blast radius, and ability to explain every observed symptom.
  3. Run the cheapest discriminating check for systemic cause surfacing; update confidence only when evidence changes.
  4. Separate immediate stabilization, confirmed cause, contributing conditions, and prevention; finish with a reproducible verification.

Deliverables

  • Facilitation structure assessment
  • Blameless framing decision and action plan
  • Systemic cause surfacing 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

Our incident reviews keep concluding that someone should have been more careful. How do we get past that?

Expected output

Human error is where analysis stops, not where it should. Ask why the action seemed reasonable at the time and what made the mistake possible, which reliably surfaces the missing guardrail, the confusing interface, or the absent verification step...

Boundaries and compatibility

Ideal for

  • Facilitation structure: produce a decision or artifact grounded in supplied evidence.
  • Blameless framing: produce a decision or artifact grounded in supplied evidence.
  • Systemic cause surfacing: 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.