25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
---
|
|
name: grill
|
|
description: >
|
|
Stress-test a fuzzy plan through questions when asked to grill, challenge, or interrogate the plan. Do not activate automatically before every spec.
|
|
scope: global
|
|
---
|
|
|
|
# Plan questions
|
|
|
|
Inspect the conversation and relevant code before asking. Infer routine details;
|
|
ask only about a product choice or uncertainty that materially changes the plan.
|
|
|
|
1. Identify the most consequential unknown about the goal, completion criteria,
|
|
scope, constraints, interfaces, or failure behavior.
|
|
2. Ask one concise question with a recommended answer and a sentence explaining
|
|
its impact. Respect the user's chosen level of detail and pressure.
|
|
3. Incorporate the answer and continue only while consequential unknowns remain.
|
|
Do useful independent investigation while waiting when possible.
|
|
4. Stop when the goal and boundaries are clear. Summarize decisions and remaining
|
|
uncertainties; distinguish deferred non-blocking questions from true blockers.
|
|
|
|
An explicit request to interrogate can use a question-at-a-time exchange. Otherwise
|
|
follow [shared workflow](../../protocols/workflow.md); routine edits and already-clear
|
|
implementation requests need no interview or mandatory handoff report.
|