grill-melisted

Settle the load-bearing questions about a request BEFORE the first line of work — the decide step's opening act. Walks the decision tree one frontier at a time: reads what the repo already answers (signed briefs and specs are closed — cited, never re-asked), then asks the unsettled decisions whose prerequisites are settled, in numbered rounds of at most five, each question carrying WHY it matters and a RECOMMENDED answer, and waits. Stops when no remaining question would change the work. Invoke it at genesis (before the intent interview) and on every brief-lane request (before the brief is drafted); the human can invoke it anytime with "grill me", "interrogate this plan", "poke holes in this", "what am I missing", "ask me the hard questions", "settle the open questions before we start". Never grills the direct lane, a bug fix, an emergency fix, or a spike. Produces no new artifact: answers land in the intent brief or the feature brief — settled decisions with their why, the human's own calls under Open decisi
kvdm-co-pilot/create-cmp · ★ 0 · AI & Automation · score 72

Install: claude install-skill kvdm-co-pilot/create-cmp

# grill-me — settle the load-bearing questions before the first line of work Your job: find the decisions this request rests on that nobody has actually made, and get them made — by the human where the call is theirs, by a recommended default where it is not — before any tool touches the tree. The output is not a transcript of questions; it is a decide-layer artifact written from settled ground. Why this exists. Every request arrives with hidden parts: the assumption the human never articulated, the step they were going to "figure out as we go", the two adjacent choices that contradict each other. Left unasked, the agent makes those calls silently mid-build, and they surface weeks later as a redesign, a re-litigated decision, or a spec that says one thing while the code does another. This harness already refuses to *sign* anything generic; the grill is the same refusal applied one step earlier — it refuses to *start* on anything unsettled. The pattern is Matt Pocock's `grill-me` (one load-bearing question at a time, recommended answer attached, nothing built until confirmed), adapted to this harness's artifacts and its standing rules: evidence-or-silence, and settled decisions are closed. ## 0. When it fires — and when it must not | Entry | Grill? | Where the answers land | |---|---|---| | **Genesis** (cmp-new) | Always — before the intent interview collects a single config answer | `specs/intent.md` sections | | **Brief lane** (new feature, change to signed behavior, arc