← ClaudeAtlas

assumption-inventorylisted

Surface and confirm the load-bearing assumptions behind a task before a long or expensive run — goal, root, what may be edited, what is off-limits, what done means, and open questions — separating what can be cited from what is being guessed, so bad direction is caught before time is burned. Also pressure-tests the plan's acceptance criteria, flagging any that are weak or built on unproven assumptions, and asks the blocking uncertainties (scope boundaries, interpretations, soft "done" bars) as structured questions. Use at the start of a multi-step or high-cost task, when resuming ambiguous or handed-off work, or whenever the target is not crisply stated and you are about to commit to a long run.
adamlinscott/claude-skills · ★ 3 · AI & Automation · score 76
Install: claude install-skill adamlinscott/claude-skills
# Assumption Inventory Before a long run, the cheapest bug to fix is a wrong premise. This skill is a **preflight**: surface the assumptions the next stretch of work rests on, separate what you can *cite* from what you are *guessing*, and confirm the load-bearing guesses before the work starts — not after the diff lands. The mechanism is one distinction held strictly: a **fact** is something on disk or stated by the user (it gets a citation); an **assumption** is everything else (it does not). The danger is an uncited assumption quietly becoming load-bearing — the work builds on it, and the divergence only surfaces hours later. This skill drags those assumptions into the open and gates the load-bearing ones on evidence or confirmation. This is the front end of the triad: `assumption-inventory` (before), `reground` (mid-drift), `fresh-eyes` (after). Run it in order; do not skip to step 4. ## 1. Decide whether to run Run this when the work ahead is long, expensive, hard to reverse, or multi-step **and** the target is not already crisply pinned. Skip it for a one-line change with an explicit target — the ceremony is not free. When in doubt on a big task, run it. ## 2. Draft the inventory Fill every slot. For each, tag the basis: `[cited: file:line / user said X]` for a fact, `[assumption]` for a guess. Do not leave a slot blank — "unknown" is a valid, important answer. - **Goal** — what outcome am I trying to produce, in one sentence? Why now? - **Root / scope** — which