premortem

Identify risks in pending design, deletion, rename, release, or workflow decisions.

9|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/corca-ai/charness --skill premortem-corca-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: premortem
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/premortem
Command: npx skills add https://github.com/corca-ai/charness --skill premortem-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Premortem helps teams examine pending decisions (design, deletion, rename, release, or workflow) before lock-in, surfacing distinct risk angles and distinguishing blockers from unwarranted worries.

Core Features & Use Cases

  • Structured, multi-angle risk analysis for pending decisions, enabling teams to surface critical failure paths.
  • Clear four-bin triage results: Act Before Ship, Bundle Anyway, Over-Worry, Valid but Defer, guiding concrete next steps.
  • Bounded, fresh-eye reviews via subagents to ensure a focused, time-boxed assessment and avoid scope creep.
  • Durable decision memory: record findings in the caller’s artifact to support future audits and rollbacks.

Quick Start

Describe the pending decision artifact and trigger a bounded premortem review to surface concerns.

Frequently Asked Questions about premortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a risk review for pending design or release decisions before lock-in?

Use a structured premortem review to analyze pending decisions from multiple angles, surfacing critical failure paths and separating real blockers from over-worry before lock-in.

What is the best way to triage identified risks in product management workflows?

Triage identified risks by sorting them into four bins: Act Before Ship, Bundle Anyway, Over-Worry, and Valid but Defer, guiding concrete next steps for product management workflows.

When do I need a premortem analysis for a pending rename or deletion decision?

You need premortem analysis when a pending rename or deletion decision has significant impact and requires multiple angles and a counterweight review to distinguish real blockers from unwarranted worries.

How does bounded subagent review work for decision-making risk assessment?

Bounded subagent reviews provide focused, time-boxed fresh-eye assessments of pending decisions, ensuring a counterweight review that avoids scope creep while surfacing distinct risk angles.

Can I maintain durable decision memory for future audits and rollbacks after risk triage?

Yes, record premortem findings in the caller's artifact to maintain durable decision memory, supporting structured scope and evidence triage for future audits and rollbacks.

What are the limitations of using a premortem approach for workflow governance?

Premortem reviews are bounded and time-boxed to avoid scope creep, meaning they focus on separating real blockers from over-worry rather than providing an exhaustive, unbounded risk inventory for workflow governance.