From workflow
Use as the mandatory evidence gate before signing off on any strategy, PRD, or business case—audits every key claim against documented sources and assigns calibrated probabilities.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow:assumption-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Assumption-audit is the "evidence gate" that prevents Resulting (evaluating decisions by outcomes) and Hindsight Bias (feeling something was predictable after it happened). It forces an honest accounting of what is known versus what is guessed.
Assumption-audit is the "evidence gate" that prevents Resulting (evaluating decisions by outcomes) and Hindsight Bias (feeling something was predictable after it happened). It forces an honest accounting of what is known versus what is guessed.
NO SIGN-OFF WITHOUT VALIDATION EVIDENCE FOR EVERY KEY CLAIM
Assertions without evidence are vulnerabilities. Unaudited assumptions create fragile strategies that collapse under the first sign of volatility.
digraph assumption_audit_flow {
"Start" [shape=doublecircle];
"Step 1: Inventory Key Assumptions" [shape=box];
"Step 2: Evidence Mapping (Knowledge Tracker)" [shape=box];
"Step 3: Stress-Test (Pre-mortem)" [shape=box];
"Step 4: Probability Calibration" [shape=box];
"Gate: Claim-Evidence Match" [shape=diamond];
"Step 5: Fragility Audit (Via Negativa)" [shape=box];
"Done: Audit Passed" [shape=doublecircle];
"Start" -> "Step 1: Inventory Key Assumptions";
"Step 1: Inventory Key Assumptions" -> "Step 2: Evidence Mapping (Knowledge Tracker)";
"Step 2: Evidence Mapping (Knowledge Tracker)" -> "Step 3: Stress-Test (Pre-mortem)";
"Step 3: Stress-Test (Pre-mortem)" -> "Step 4: Probability Calibration";
"Step 4: Probability Calibration" -> "Gate: Claim-Evidence Match";
"Gate: Claim-Evidence Match" -> "Step 5: Fragility Audit (Via Negativa)" [label="matched"];
"Gate: Claim-Evidence Match" -> "Step 1: Inventory Key Assumptions" [label="mismatch"];
"Step 5: Fragility Audit (Via Negativa)" -> "Done: Audit Passed";
}
REQUIRED SUB-SKILL: using-skills — To maintain audit discipline.
RECOMMENDED SUB-SKILL: devils-advocate — To provide adversarial pressure on the assumptions.
RECOMMENDED SUB-SKILL: decision-frameworks — To structure the final sign-off.
| Thought | Reality |
|---|---|
| "We've done our research, we know this will work." | This is "definite optimism" and ignores the role of luck and hidden volatility. |
| "I don't need a knowledge tracker; I remember why I chose this." | Memory is a "hindsight bias" machine that rewrites history to make you look right. |
| "A pre-mortem is too negative; it will demoralize the team." | Unchecked fragility is what actually demoralizes teams when they inevitably fail. |
| "The upside is so high it doesn't matter if we're slightly wrong." | Fragile systems have a "concave" downside—being "slightly wrong" can lead to total ruin. |
These thoughts mean STOP — you are about to shortcut:
npx claudepluginhub joellewis/skill-library --plugin workflowUse this skill when the user asks to "map assumptions", "identify assumptions", "what are we assuming", "assumption audit", "what could go wrong with this idea", "test our assumptions", "what do we need to validate", "identify our riskiest assumption", or when reviewing an idea or PRD and wants to surface hidden bets before building. Do NOT use this skill for general risk analysis — that is part of the pre-mortem skill.
Analyzes plans via pre-mortem: extracts assumptions across market/execution/customer/competitive/financial/dependency categories, rates confidence and impact, maps high-risk vulnerabilities. Run before resource commitment or presentations.
Extracts and risk-rates hidden assumptions in product briefs or PRDs across desirability, feasibility, viability, and usability categories. Outputs a prioritized map with confidence and impact scores.