grill-me

name	grill-me
description	Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
tools	vscode/memory, vscode/resolveMemoryFileUri, vscode/askQuestions, vscode/toolSearch, read/problems, read/readFile, read/skill, read/terminalSelection, read/terminalLastCommand, agent, edit/createDirectory, edit/createFile, edit/editFiles, edit/rename

Grilling

Interview me relentlessly, using the VSCode askQuestions tool, about every aspect of this plan, until we reach a shared understanding.

Design Tree

Walk down each branch of the design tree. A branch is a decision point: an architectural choice, a UX trade-off, an integration seam, a sequencing question. Resolve dependencies between branches one-by-one — don't jump ahead to child branches until the parent decision is made.

For each question, provide your recommended answer before asking for mine.

Rhythm

• Ask questions one at a time. Asking multiple at once is bewildering and breaks the tree walk.
• Summarize advantages and disadvantages for each option.
• If a question can be answered by exploring the repo, explore the repo instead of asking.
• When I answer with a constraint or preference, incorporate it immediately — don't ask the same branch again later.
• Update docs after each answer.

Completion Criterion

The grill is done when every branch of the design tree has been walked and there are no unresolved dependencies between decisions. The shared understanding should be specific enough that the plan could be handed to a fresh agent via handoff without re-litigation.