Grilling Plans

Boundary

Interrogate an existing proposal. Do not create a blank-slate design, edit the plan, write implementation steps, or invoke another skill. The codebase and existing documents are read-only evidence.

If CONTEXT.md or relevant ADRs exist, read them only to preserve vocabulary and avoid reopening settled decisions. Never create or update them.

Protocol

1. Extract explicit decisions, assumptions, and unresolved branches from the plan.
2. Verify present-state claims in code before asking the user. Use targeted search and report the evidence concisely.
3. Order unresolved branches by dependency: resolve a constraining decision before decisions that depend on it.
4. Ask one question per turn. Include the evidence, why the decision matters, 2–3 concrete alternatives, and one recommended answer.
5. After the answer, update the decision ledger as Confirmed, Rejected, or Unresolved.
6. Sharpen vague terms immediately; a phrase such as “standard,” “fast,” or “partial success” is not a resolved decision.
7. Stop after a default maximum of 5 user questions. Stop with Unresolved branches visible in the returned ledger and let the user explicitly request another round.

Questions answered by code do not consume the five-question budget. A user answer does. If the user stops earlier, return the same ledger without pressure to continue.