grill-with-docs

To surface ambiguities in project plans, you challenge every decision against domain terminology and existing documentation like CONTEXT.md and ADRs, resolving inconsistencies by capturing explicit choices inline.

Align CONTEXT.md and ADRs by relentlessly challenging plan decisions against domain language, then updating the documentation inline as decisions crystallize to capture explicit choices and surface inconsistencies.

Validating domain terminology against the codebase involves exploring repository structure to check that project plans and documentation like CONTEXT.md accurately reflect the actual terms used in the code.

Update ADRs and CONTEXT.md during project planning when you need to resolve misalignments, surface explicit choices, and ensure terminology consistency as decisions crystallize through probing sessions.

Yes, domain language probing finds inconsistencies by relentlessly challenging plan decisions against existing documentation and domain terminology, guiding inline updates to CONTEXT.md and ADRs as decisions are made.

Yes, grill-with-docs works with CONTEXT.md and ADR files by stress-testing project plans against them, surfacing ambiguities, and guiding inline documentation updates as decisions crystallize.