1.2 KiB
1.2 KiB
name, description, scope
| name | description | scope |
|---|---|---|
| grill | Stress-test a fuzzy plan through questions when asked to grill, challenge, or interrogate the plan. Do not activate automatically before every spec. | 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.
- Identify the most consequential unknown about the goal, completion criteria, scope, constraints, interfaces, or failure behavior.
- Ask one concise question with a recommended answer and a sentence explaining its impact. Respect the user's chosen level of detail and pressure.
- Incorporate the answer and continue only while consequential unknowns remain. Do useful independent investigation while waiting when possible.
- 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; routine edits and already-clear implementation requests need no interview or mandatory handoff report.