grill-me

grill-me

grillreadhands-on

Use this when: you want a plan stress-tested by interview

Problem it solves — A plan you only roughly have ships with its gaps intact. This interviews you relentlessly — one recommended-answer question at a time, walking every branch of the decision tree — until the design is hardened and the unknowns are gone.

Grill me

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead of asking.

Pin the non-goals, not just the goals. Before you close, ask explicitly what this work won't do and record it — half of misalignment is silent disagreement about scope edges, not about the goal itself, and an unnamed non-goal is the one that quietly gets built. A plan with its out-of-scope edges named is far harder to drift.

Where the plan's blast radius warrants, draw question angles from the adversarial lens deck (docs/agents/lens-deck-adversarial.md) — the maintainer-in-six-months, the on-call-at-3am, the misuse case — as framings for what to ask next, never as verdicts; this stays a collaborative interview, not a red-team.

Where it sits

• Not brainstorm — that captures a fuzzy idea and pins it into a spec behind a hard gate; grill-me pressure-tests a plan you already roughly hold.
• Not check-reasoning — that's a blind, adversarial pass/fail gate (a subagent that never saw your reasoning); grill-me is a collaborative interview that recommends answers as it goes.
• Domain/terminology-heavy plan? Use grill-with-docs, which also sharpens the glossary and writes CONTEXT.md / ADRs inline.