grill-with-docs

To stress-test a project plan, you can grill your plan against existing domain models by systematically questioning every assumption and decision path. This process exposes gaps and ambiguities, updating documentation inline as conclusions crystallize.

Updating CONTEXT.md and ADRs while refining a domain model is best handled by applying a relentless grilling process to your decisions. As terminology and architecture decisions crystallize, the documentation is updated inline to capture explicit answers.

You can identify ambiguities in architectural decisions by examining every assumption and decision path through a structured grilling session. This method captures interactions as explicit questions with recommended answers, exposing hidden gaps before implementation.

Yes, you can explore the codebase to ground architectural decisions during a documentation review. The grilling process supports codebase exploration to ensure that domain terms and design decisions align with the actual implementation.

You should use an ADR grilling session when you need to iteratively refine domain terms and design decisions for clearer communication. It is ideal when you want to challenge a plan against documented architecture and update records inline.