grill-with-docs

Relentless design interrogation that stress-tests plans against your domain model and sharpens terminology inline.

- Explores your codebase to ground discussions in existing code, glossaries (CONTEXT.md), and architectural decisions (ADRs)

- Challenges fuzzy language, resolves terminology conflicts, and updates your domain glossary as decisions crystallize

- Tests design decisions against concrete scenarios to expose edge cases and boundary violations

- Creates or updates CONTEXT.md and ADRs only when warranted, keeping documentation lean and decision-focused

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Most repos have a single context: