/grill-with-committee
Call the Skill tool with grilling, passing the current decision context. Substitute committee
voting for its answer slots: unanimous enumerated answers are accepted silently; a split or
any "Other" vote escalates to the human.
A unanimous committee answer occupies the user-answer slot that grilling normally waits
for. Apply the same consensus rule to its final shared-understanding confirmation, preserving
the no-human path when all three voters agree.
Usable standalone (ending in a grill.md digest) or embedded as the grill phase of
/loop-plan-semiauto. You drive every round; only you talk to the user — the voters are
autonomous leaves that only vote.
When embedded, accept only the planner's release decisions as the frontier. An explicitly deferred implementation hypothesis is already resolved for planning purposes. A unanimous vote settles the decision and its provenance; committee agreement alone never creates acceptance authority.
The round loop
Repeat until nothing is open:
- Form the frontier with
grilling. Pass it the current decision context. Do not vote on facts. - Make the answers votable. For each frontier question, frame 2–4 mutually exclusive
options plus an "Other" hatch. Give each option a short
idand name your recommendation. - Spawn the three review agents to vote at once —
subagent_type: architecture-review,rules-enforcer,general-review. Each already carries its lens; in the spawn prompt tell it it's a committee voter, not a reviewer — vote on this batch from your lens and return a choice per the vote contract (below), not findings. Hand it the batch (the questions, their options + ids, and the plan/context). If asubagent_typeis missing, stop and tell the user; don't run a partial committee. - Apply consensus (a plain compare of the three
choicestrings): all three the same enumerated id → accept, provenancecommittee. Anything else → escalate to you with the options, the vote breakdown, and each lens's rationale, provenancehuman. An "Other" is never an enumerated id, so any "Other" escalates too. - Model + continue. Call the Skill tool with
domain-modeling, passing the resolved terms and decisions, then feed the answers back intogrilling. Continue untilgrillingreaches its completion condition.
Standalone output — grill.md
Standalone, write a grill.md digest to a per-run folder ~/.grill/<repo-key>/<run-key>/
(host-neutral; mint <run-key> from the topic and disambiguate if it exists, so concurrent
grills don't collide), and print the path. Each entry: the resolved question, its answer, and
its provenance (committee = unanimous, human = escalated). Embedded in
/loop-plan-semiauto, skip the file — the decisions feed the host's draft phase under the
host's run folder.
GLOSSARY.md / ADR updates from domain-modeling are not per-run — they're the repo's
durable docs in the working tree, intentionally shared.
Vote contract
Paste this into each agent's spawn prompt (step 3) — it's the choice shape they return.