grill-with-docs

Validate architecture decisions by running an interactive grilling session that probes your proposed plan against your repository's CONTEXT.md and ADRs. The assistant questions design assumptions to surface ambiguities, clarify dependencies, and enforce terminology alignment with the current domain model.

An ADR grilling session is an interactive interrogation of your design assumptions against existing architecture decision records and domain docs. It relentlessly probes every branch of a proposed plan to reveal gaps, enforce live documentation updates, and help teams converge on a shared architectural direction.

Keep CONTEXT.md updated by using a guided grilling session that proposes inline documentation updates as decisions crystallize. The assistant explores the codebase for consistency and automatically updates domain docs and ADRs while you clarify dependencies and align terminology.

Yes, you can surface inconsistencies in your domain model before coding by interactively interrogating your design assumptions against existing documentation. The grilling process reveals gaps and ambiguities in your CONTEXT.md and ADRs, ensuring terminology alignment and architectural consistency.

The best way to challenge a proposed architecture plan is to start a grilling session where the assistant questions each branch of your design against existing ADRs and CONTEXT.md. This guided questioning reveals gaps, clarifies dependencies, and enforces live documentation updates as decisions are made.

Yes, you need existing ADRs and a CONTEXT.md file to effectively validate your architecture plan. The grilling session relies on probing your proposed design against these repository domain documents to surface inconsistencies, align terminology, and propose inline updates as decisions crystallize.