grill-with-docs

To stress-test your plan against a domain model, run a guided grilling session that uses relentless questioning to surface ambiguities and misalignments, ensuring terminology is sharpened and decisions are captured in CONTEXT.md.

Update ADRs during domain modeling when decisions crystallize during a plan validation session. Propagating these changes to repository documentation ensures architectural choices remain aligned with the clarified domain boundaries.

Yes, you can enforce terminology discipline by inspecting the codebase for supporting evidence. This guided codebase exploration validates that domain boundaries and terms in your CONTEXT.md accurately reflect the implementation.

The best way to surface misalignments between requirements and domain boundaries is through domain-clarification questioning. This approach challenges your plan against the existing domain model and updates documentation inline as decisions crystallize.

Yes, updating context artifacts works without external dependencies. The grilling process relies on guided codebase exploration and decision crystallization to directly update CONTEXT.md and ADRs within your repository.