grilling

Grilling resolves consequential unknowns, not every detail. Allow no production code or implementation while a material user-reserved decision is open. Invocation does not authorize delegation.

1. Build evidence

Read the request, plan, repo, tests, docs, references, and decisions. Facts are the agent's job; ask only for preferences, scope, risk appetite, or decisions evidence cannot answer. Name the blind spot most likely to invalidate the direction. Prototype when behavior answers faster than prose.

/brain-dump is optional. Preserve every opportunity track and start from its Answer ledger: never re-ask Settled entries; challenge Tentative only when downside matters; ask Unknown only when it could invalidate or prioritize a track.

2. Explore mode

With no direction, present 2-3 approaches with trade-offs, reversibility, evidence, and a recommendation. Route competing plans to /plan-arbiter. Challenge variant: with a direction, steelman the best alternative and say what would make it wrong.

For customer-facing UI, show an ASCII wireframe before questions. Sketch each materially different layout in a fenced text block with real labels, controls, grouping, order, and fixed/scroll regions. Keep borders aligned; treat it as structure, not pixel accuracy. Show desktop and mobile only when composition changes. Shared layouts need one sketch plus deltas.

Map a decision tree to its currently answerable frontier. Ask the whole frontier in one numbered round using this Question format:

**Q1 -- <question title>**
<question or choices>