grill-with-docs

A Simplified-Chinese grilling skill that stress-tests a plan by interrogating it against a project's existing domain model and documented decisions, sharpening terminology and updating documentation inline as decisions crystallize. It is used when someone wants their plan challenged against their project's own language and recorded decisions. The interaction style is deliberate: it asks one question at a time and waits for feedback before continuing, works down each branch of the design tree resolving dependencies between decisions, always offers its own recommended answer, and, when a question can be answered by exploring the codebase, investigates the code instead of asking.

It builds domain awareness from existing documentation. In most repos that means a single CONTEXT.md glossary plus architecture decision records under docs/adr/; when a CONTEXT-MAP.md exists at the root, the repo has multiple bounded contexts, each with its own CONTEXT.md and ADR folder, and the map points to them. Files are created lazily, a CONTEXT.md only when the first term is resolved and an ADR folder only when the first ADR is needed.

During a session it applies several tactics. It challenges terminology that conflicts with the existing glossary, for example when the user's meaning of cancellation differs from the documented definition; it sharpens fuzzy or overloaded terms toward a precise canonical one, such as distinguishing account as Customer versus User; and it stress-tests domain relationships with concrete, invented scenarios that probe edge cases and boundaries between concepts. It cross-references explanations against the code and points out contradictions, such as code that cancels whole orders when the user claims partial cancellation is possible. Resolved terms are captured in CONTEXT.md immediately using a defined format, and the glossary is kept purely as a glossary with no implementation detail, specs, or scratch notes. ADRs are proposed sparingly, only when a decision is hard to reverse, surprising without context, and the result of a real trade-off; if any of those three is missing, it skips the ADR. Dedicated format files (CONTEXT-FORMAT.md, ADR-FORMAT.md) define the output.