grilling

name	grilling
description	Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions.

Question format

Every question carries its own evidence — I judge the tradeoff itself, never a paraphrase of it:

1. Context — encode the problem. Show the real thing: actual code with file:line references, real snippets, and a diagram (mermaid / sequence / ASCII — anything that renders) when it clarifies.
2. Options — each candidate as concrete code or a concrete diff sketch, not a prose description of an approach.
3. Rubric — grade the options against the rubric that best fits this question (e.g. floor-first, reversibility, blast radius, correctness, parallelizability, fit with what's already there — pick what applies).
4. Recommendation — which option and why.

Batching

Batch independent questions into one round; a question whose answer depends on another waits for the next round. A batch of independent questions saves round-trips; a dependent question asked early is answered blind.

Facts vs decisions

If a fact can be found by exploring the environment (filesystem, tools, docs), look it up rather than asking me. The decisions are mine — put each one to me and wait for my answer.

Do not act until I confirm we have reached a shared understanding.