agentsclimarketplace

Incident postmortem

Skill planifest/planifest-framework/planifest-framework/external-skills/incident-postmortem

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill incident-postmortem

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Incident postmortem workflow for evidence-backed root cause analysis and systemic prevention actions. Use after incident stabilization when teams need timeline, root-cause chain, contributing factors, and owned prevention actions; do not use for active incident command and real-time mitigation.

SKILL.md

2.2 KB, as published. Nobody here has run it

Incident Postmortem

Overview

Use this skill to turn incidents into concrete learning and prevention changes, not just narrative summaries.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Root-cause evidence rules:
    • references/root-cause-evidence-rules.md

Templates And Assets

  • Postmortem report template:
    • assets/postmortem-report-template.md
  • Incident timeline template:
    • assets/incident-timeline-template.csv
  • Corrective action tracker:
    • assets/corrective-action-tracker-template.csv

Inputs To Gather

  • Incident timeline signals and operational evidence.
  • Customer/business impact and severity context.
  • Mitigation and recovery actions taken.
  • Known system/process constraints.

Deliverables

  • Evidence-backed postmortem report.
  • Timeline artifact linking events to signals.
  • Corrective action plan with owner, due date, and verification.
  • Residual risk statement and follow-up tracking.

Workflow

  1. Build timeline in assets/incident-timeline-template.csv.
  2. Analyze trigger, root causes, and contributors using references/root-cause-evidence-rules.md.
  3. Draft report in assets/postmortem-report-template.md.
  4. Track prevention actions in assets/corrective-action-tracker-template.csv.
  5. Publish and align owners on verification timelines.

Quality Standard

  • Root cause is evidence-backed, not speculative.
  • Timeline and impact statements are explicit and auditable.
  • Corrective actions are specific, owned, and verifiable.
  • System/process improvements are prioritized over blame narratives.

Failure Conditions

  • Stop when root-cause claims lack supporting evidence.
  • Stop when action items have no owner or verification method.
  • Escalate when residual risk exceeds accepted reliability policy.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.