Grill Me

Use before consequential implementation, architecture, integration, data, security, or workflow decisions. This is interview and planning, not implementation.

Load evidence and questions first. Use nearest applicable domain context, glossary, architecture docs, decision records, and code. Do not invent domain vocabulary or private path assumptions.

State machine

prepare → question → checkpoint → next-question | output-plan → waiting:user-approval → complete

Ask exactly one highest-risk unresolved question per turn. Do not batch questions or smuggle recommendation into question. Before each question, state evidence source, remaining unknown, and consequence. Ask user only for preference, priority, risk tolerance, ownership, or fact unavailable in artifacts.

Coverage

Progress through relevant topics, skipping only with evidence: goal and success metrics; users/domain terms; current behavior and constraints; boundaries and failure modes; authorization/privacy/data lifecycle; contracts and compatibility; state/concurrency/idempotency; migration/rollback; observability/support; testing/acceptance; ownership and rollout risk.

Call out conflict between user wording and authoritative terminology immediately. Propose canonical term and record resolution. Probe concrete edge cases rather than abstract concerns.

Checkpoint