grill-with-docs

To stress-test a design plan against your domain model, use an interactive grilling session that asks clarifying questions one at a time. This process challenges your plan against repository language and documented decisions, resolving ambiguities by walking through each design tree branch.

The best way to resolve domain-level ambiguities is through an iterative interview process that explores design branches individually. By relentlessly questioning the plan against the repository's existing language, you establish a shared understanding and update documentation inline as decisions crystallize.

You can update CONTEXT.md and ADRs inline by walking through each design tree branch and capturing decisions as they crystallize. The grilling session updates these documentation files directly during the interactive domain alignment process.

Yes, you can use an interactive interview to align domain terminology with codebase context. If a question about terminology can be answered by exploring the codebase, the session explores the codebase directly instead of asking, ensuring documentation matches actual implementation.

You should use an interactive grilling session when you have a plan that needs validation against your repository's language and documented decisions. It is ideal for capturing live documentation updates and iteratively resolving dependencies between design decisions.

No existing documentation files are strictly required to begin, but the session actively updates CONTEXT.md, CONTEXT-MAP.md, and ADRs inline as decisions are made. It uses your repository's current language to challenge the plan and establish a shared understanding.