grill
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.
npx skills add JuliusBrussee/cavekit --skill grill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 new` on 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: 1. How well does user know this domain? (sets question depth) 2. How locked is the idea? (exploring vs committed) 3. 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. 1. **Goal** — what must the code *do*, in one line? (→ §G) 2. **Done** — how do we know it wo
- WHEN TO GRILL
- CALIBRATE FIRST
- QUESTION LADDER
- ANSWER FORMAT
- HANDOFF
- WHEN TO STOP
- BOUNDARIES
What does the grill skill do?
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.
How do I install it?
Run `npx skills add JuliusBrussee/cavekit --skill grill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From JuliusBrussee/cavekit, a repository with 1,133 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.