← ClaudeAtlas

assumption-checklisted

Pressure-test the assumptions behind a plan, claim, or decision against actual data before acting on it. Use when /assumption-check is invoked, or when Shane says "check my assumptions", "is this actually true", "what does the data say", "sanity-check this against the numbers", or before committing to a plan built on a belief nobody has measured. Do NOT use for steelmanning an opposing view (use /challenge) or for finding contradictions across vault notes (use /contradict).
slogsdon/skills-workflows · ★ 0 · AI & Automation · score 68
Install: claude install-skill slogsdon/skills-workflows
# Skill: /assumption-check [plan, claim, or doc] Separate what Shane *believes* from what the data *shows* — the value is catching the load-bearing assumption that's never been checked before it costs a week of work. **Don't:** treat every assumption equally — rank by how much the plan collapses if it's wrong, and check the top 3 first. **Don't:** call an assumption "validated" from a single anecdote or one data point; say "supported by [source], thin" instead. **Don't:** go looking for data that confirms — state what result would *disprove* each assumption before checking. ## Steps 1. **Extract.** List every assumption the input rests on, explicit and implicit. Phrase each as a falsifiable statement. 2. **Rank.** Mark each as load-bearing / supporting / cosmetic. Only load-bearing ones get checked by default. 3. **Define the test.** For each, name the data that would confirm or kill it, and where it lives. 4. **Check.** Pull the data. Record the actual number or finding, with source. 5. **Verdict.** Per assumption: Holds / Weak / Contradicted / Untestable-with-current-data. 6. **Output** a table (assumption · verdict · evidence · source), then one line: what changes about the plan.