Grill
Calibrated interrogation of a fuzzy idea before it becomes a spec.
Install
npx skills add JuliusBrussee/cavekit --skill grill -g -a claude-code -y- Repository
- JuliusBrussee/cavekit1.2k
- Category
- Testing
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 681 tokens
- Runs scripts
- No, instructions only
What it does
Calibrated interrogation of a fuzzy idea before it becomes a spec. Asks one question at a time, recommends an answer, and lands each answer in §G (goal) or §C (constraints), unknowns parked as `?` items, never guessed. The cheapest place to kill a bad idea is before §T exists. Triggers when the user has a vague idea, says "grill me", "stress-test this", "challenge my plan", "interview me before I spec", or invokes /ck:grill. Defers the actual write to the spec skill.
grill, sharpen idea before spec
One question at a time. Every answer lands in a § or gets parked ?. Never guess a constraint into existence.
Plan-then-execute guesses the fuzzy parts & builds the wrong thing. Grill drags the fuzz into §G/§C before a single §T row exists. A bad assumption caught here costs one question. Caught in §B it costs a bug.
WHEN TO GRILL
- Idea is one sentence & you can feel the holes.
- Multiple readings of the goal exist & you are about to pick one silently.
- Before
/spec newon anything non-trivial. - User asks to be challenged / stress-tested.
Skip for a typo or a one-line fix. Grill scales to uncertainty, ⊥ to ego.
CALIBRATE FIRST
One opening read, not a quiz:
- How well does user know this domain? (sets question depth)
- How locked is the idea? (exploring vs committed)
- Pressure wanted: light / normal / brutal.
Match it. Brutal grilling on a half-formed idea just demoralizes. Light grilling on a committed plan misses the load-bearing flaw.
QUESTION LADDER
Climb in order. Each rung, ask one question, recommend an answer, wait.
- Goal, what must the code do, in one line? (→ §G)
- Done, how do we know it works? name the observable. (→ §C / future §V)
- Boundary, what is explicitly out of scope? (→ §C)
- Lock, what tech/lib/pattern is non-negotiable? what is forbidden? (→ §C)
- Surface, what does the outside world touch, cmd, api, file, env? (→ §I)
- Edge, the one input that breaks the happy path? (→ future §V)
- Unknown, what do we not know yet? (→ park as
?§C bullet)
Stop climbing the moment the spec would be unambiguous. Do not ask all seven by reflex.
ANSWER FORMAT
Each question carries a recommended answer so the user can grunt "yes" & move:
Q: auth, session cookie or JWT? rec: JWT, stateless, you named horizontal scaling as a §C. (a) JWT (b) cookie (c) something else?
