SkillVaultskills Browse all 500 skills

Reliability · Version 1.1.0 · Reviewed 2026-08-02

Postmortem Action Tracker

Reduce production risk in action quality and ownership assignment with evidence, explicit trade-offs, and a verification plan.

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

Turns postmortem findings into tracked, verifiable actions that do not quietly expire.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Action quality
  • Ownership assignment
  • Completion verification

How Postmortem Action Tracker works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind action quality

It decides

A ownership assignment plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Postmortem Action Tracker turns postmortem findings into tracked, verifiable actions that do not quietly expire. Use it when the work involves Action quality, Ownership assignment, Completion verification.

  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. Establish what is actually true about action quality from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind ownership assignment rather than restating the symptom.
  3. Choose the smallest defensible change for completion verification, weighing impact, confidence, effort, and reversibility.
  4. Define measurable ownership and verification

Deliverables

  • Action quality assessment
  • Ownership assignment decision and action plan
  • Completion verification 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

We write good postmortems but the action items never get done and the same incidents recur.

Expected output

Recurrence is the evidence that the actions were never real commitments. Require an owner, a verification signal, and a date on every item, cap the number so they are achievable, and review open items in the same forum that reviews new incidents...

Boundaries and compatibility

Ideal for

  • Action quality: produce a decision or artifact grounded in supplied evidence.
  • Ownership assignment: produce a decision or artifact grounded in supplied evidence.
  • Completion verification: 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 custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

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.