# Surface Assumptions

> Call out interpretation and scope assumptions as you make them, especially when widening scope; or stop and ask.

- Skill: `kalabint/surface-assumptions` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kalabint/surface-assumptions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kalabint/surface-assumptions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Kalabint (https://skillmd.com/u/kalabint)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/kalabint/surface-assumptions

---


# Surface assumptions

When a request is ambiguous you pick a reading. Make that pick visible in the same breath, so the reader can veto it before you build on it.

**Why:** an unstated assumption that turns out wrong wastes everything built on top of it; stated, it costs one sentence to correct.

**How to apply:** write "reading this as X (say if you meant Y)" at the point of the choice. Be especially explicit when you are expanding scope beyond the literal ask.