assumption-surfacing
Assumption Surfacing
Enumerate the implicit assumptions a spec, plan, design, or estimate silently depends on, and decide for each whether it must be verified before building or can be consciously accepted with a named risk. Unsurfaced assumptions become mid-build surprises; surfaced ones become a checklist.
When to Use
Use before implementation starts, when a spec, plan, design doc, or estimate is about to be committed to. Out of scope: verifying the assumptions themselves (this skill produces the verification worklist, not its results), reviewing finished code, challenging whether the work should happen at all, and general red-team critique of the design's decisions — this skill only extracts unverified premises the plan depends on.
Required Inputs
- The spec, plan, design, or estimate text.
- Optional: system context (architecture notes, known constraints, prior incidents); used to ground assumptions, never required.
If no text is provided, emit the BLOCK template; do not invent a plan to analyze.
Assumption Categories
Sweep the text once per category. For each, ask: what must be true for this plan to work that the text does not state or verify?