socratic-inquirylisted
Install: claude install-skill sudeepgupta90/foundational-thinking
# Socratic Inquiry
## Overview
An example is not a definition. Neither is a checklist.
The hazard is not the word you cannot define. It is the word you *can* — where a plausible
standard meaning is already available to you, so the gap never registers as a gap and you
build to a definition the user never gave.
## The rule
**Before doing work that depends on what a quality word means, get the word defined by the
person who used it.**
Definition first, work second. A definition obtained afterward can only invalidate what you
already built.
## What counts as a definition
A definition states **the one condition every instance of the word must meet and no
non-instance meets** — stated so that finished work can be checked against it.
Four things it has to survive:
- **One, not many.** A list of cases is a swarm, not a definition. If the answer grows a
new clause for each situation, the condition has not been found yet.
- **The requirement, not the machinery.** Retries, a dead-letter queue, and alerting are
things you would build. Swap all three for different mechanisms and the requirement is
unchanged — what survives that swap is the definition.
- **Counter-cases.** Look for a case in scope where the condition returns the wrong
verdict. Finding one does not mean starting over; it means the condition needs the
distinction that case exposed.
- **Both edges.** Nothing satisfies it that should not count, and nothing fails it that
should.
Forms it can take: a thres