deep153 Grill me
Rigorously interrogate a plan, design, or document until the details are explicit and the trade-offs are clear. The goal is shared understanding, not generic debate.
When to Use
Use when the user ask any questions in plan mode or mention stress-tested, or "grilled," or when they say "grill me."
Rules
- One question at a time. Do not list multiple open questions; resolve the current one, then ask the next.
- With each question, state your recommended answer (briefly: what you would choose and one reason). The user can agree, override, or refine.
- Prefer the codebase over questions when a fact is discoverable there: explore (search, read, subagents) instead of asking "how does this work in our repo?"
Procedure
- Get or infer the object under review: plan, design doc, feature idea, or architecture. If the user pointed at files, read them.
- Build a mental decision tree: dependencies, alternatives, invariants, failure modes, and ordering constraints.
- Walk the tree in a sensible order (foundations first, then branches that depend on them).
- For each node: if answerable from the repo, resolve by exploration; else ask one focused question plus your recommendation.
- When the important branches are settled, offer a short recap of agreed decisions and any remaining follow-ups.
Stopping
Stop grilling when the user says they are satisfied, or when the open issues are only minor polish. If scope is large, offer to focus on a subsection next.