grill-with-docs-batchlisted

# Grill With Docs Batch Challenge a plan against the repository's domain model and documentation like `grill-with-docs`, but move in small coherent batches instead of one question at a time. ## First Decide Whether To Stop Before asking any batch, run a saturation audit: - Read the target plan/ADR/spec and the domain glossary or context file it depends on. - Check recent git history for the same target docs when available, but use it only as supporting evidence. Commit count is not a stop condition by itself; it helps find decisions that were already made and areas that may be getting re-litigated. - Separate durable decision questions from implementation defaults. Do not ask the user to discuss things the implementation can decide locally without changing public contracts, private-data boundaries, safety policy, cost/model infrastructure, or irreversible file moves. - If an ADR is accepted, a plan names what changes, what is out of scope, the important boundaries, the acceptance gates, and the next execution step, and local docs/code do not contradict it, answer that no more discussion is needed. When the user asks whether remaining questions exist, answer the yes/no first. Only ask a batch if at least one unresolved question would materially change the plan, contract, public/private boundary, or acceptance gate. ## Decision-Impact Test Before asking a question, state why its answer matters. A question is worth asking only when a concrete answer coul