agentleFS
hranesshraness/personal-monorepo-template/.agents/skills/assumption-audit/SKILL.md

assumption-audit

Skill4 starsChanged 49 days agoMITView on GitHub

Extract every assumption hidden in a claim, plan, or belief, classify each by load-bearingness and testability, and identify which single assumption would collapse the whole structure if false. Use when a plan feels solid but untested, or before committing to a decision built on unexamined premises.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to surface and stress-test the premises hiding inside a claim, plan, or belief.

    line 8
  2. Distinctive:

    Load: if this is false, does the plan break entirely, degrade, or barely notice?

    line 25
  3. Distinctive:

    Use this concise structure unless the user asks otherwise:

    line 34
  4. Distinctive:

    Do not pad the register with trivially safe assumptions to look thorough.

    line 59
  5. Distinctive:

    If everything checks out, say so — the audit passing is a valid result.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Assumption Audit

Use this skill to surface and stress-test the premises hiding inside a claim, plan, or belief. Most plans fail not at the visible steps but at an assumption nobody wrote down.

Purpose

Every plan is a conclusion resting on premises, most of them implicit. An assumption audit makes the full list explicit, sorts it by how much weight each premise carries and how cheaply it can be tested, and names the keystone — the single assumption whose failure takes the whole structure down. This converts vague confidence into a concrete testing agenda.

Procedure

  1. State the claim, plan, or belief being audited.
  2. Extract assumptions exhaustively. Look in these categories:
    • Factual: things believed true about the world
    • Causal: "doing X will produce Y"
    • People: what others want, know, or will do
    • Continuity: "current conditions will persist"
    • Capability: "we can execute this part"
    • Definitional: the framing of the problem itself
  3. For each assumption, rate:
    • Load: if this is false, does the plan break entirely, degrade, or barely notice?
    • Confidence: how strong is the actual evidence (not the felt certainty)?
    • Testability: can this be checked cheaply, expensively, or only in hindsight?
  4. Identify the keystone: highest load × lowest confidence.
  5. Propose the cheapest test for the keystone and the top 2–3 risky assumptions.
  6. State what the plan looks like if the keystone fails — is there a fallback?

Output format

Use this concise structure unless the user asks otherwise:

## Claim / plan under audit
...

## Assumption register
| # | Assumption | Category | Load | Confidence | Testability |
|---|---|---|---|---|---|
| 1 | ... | Causal | Breaks plan | Low | Cheap |

## Keystone assumption
...

## Cheapest tests
- ...

## If the keystone fails
...

Guardrails

  • Include at least one definitional assumption — the framing of the problem is always an assumption.
  • Rate confidence by evidence, not by how long the assumption has been held.
  • Do not pad the register with trivially safe assumptions to look thorough; focus on the load-bearing ones.
  • If everything checks out, say so — the audit passing is a valid result.

Canonical questions

  • "We're about to spend 6 months building this feature — sanity-check the plan."
  • "My startup thesis is that restaurants will pay for X."
  • "I'm planning to move to Austin for the lower cost of living."
  • "Our hiring plan assumes we close the Series A by Q3."
  • "I believe my best customers come from word of mouth."

Poor fits: decisions already made and irreversible (use inversion for damage control instead), and pure preference questions with no factual premises.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.