Stats
Actions
Tags
From ck
Sharpens vague ideas into clear goals and constraints through structured one-question-at-a-time interrogation before writing a spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ck:grillThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**One question at a time. Every answer lands in a § or gets parked `?`. Never guess a constraint into existence.**
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.
/spec new on anything non-trivial.Skip for a typo or a one-line fix. Grill scales to uncertainty, ⊥ to ego.
One opening read, not a quiz:
Match it. Brutal grilling on a half-formed idea just demoralizes. Light grilling on a committed plan misses the load-bearing flaw.
Climb in order. Each rung, ask one question, recommend an answer, wait.
? §C bullet)Stop climbing the moment the spec would be unambiguous. Do not ask all seven by reflex.
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?
When done, emit a compact block — goal line, constraint bullets, surfaced
unknowns as ? — and hand to the spec skill to write §G/§C. Grill proposes;
spec is the sole mutator. Never write SPEC.md directly.
Done when ALL hold:
?.Unresolved blocking unknown that needs the outside world → recommend /research, not a guess.
npx claudepluginhub juliusbrussee/cavekit --plugin ckGuides pre-implementation design exploration by asking one question at a time to produce a written spec before any code is written.
Guides users through structured dialogue to turn fuzzy ideas into concrete, implementation-free project specs. Focuses on WHAT/WHY, never HOW.
Clarifies vague requests via Socratic questioning, focusing on one key uncertainty (goals, scope, constraints, completion criteria) at a time to produce actionable requirements. Activates on deep-interview requests or unclear specs.