grill-with-docs

Validating an implementation plan against domain modeling decisions requires breaking the design tree into dependencies and resolving each trade-off iteratively. The process cross-references your CONTEXT.md glossary and ADRs to ensure terminology alignment.

Aligning architecture requirements with a domain glossary involves detecting conflicting terms against documented CONTEXT.md files. Canonical terminology is proposed inline, and the documentation updates occur directly when terms are resolved during the interrogation process.

Creating an Architecture Decision Record is needed when a true domain modeling trade-off is resolved during plan interrogation. ADRs are created sparingly to document significant architecture decisions rather than minor terminology updates.

Updating CONTEXT.md inline while clarifying architecture requirements is fully supported. As requirements clarification resolves conflicting terminology, the glossary updates are applied directly to maintain strict domain language alignment.

Context mapping resolves trade-offs across multiple architecture branches by applying iterative, one-question-at-a-time interrogation. This workflow forces explicit resolution of dependencies and documents the outcome using ADR-format guidance when necessary.

An existing ADR workflow is not strictly required to function, but having documented architecture decisions enhances the validation process. The skill provides ADR-format guidance and creates records sparingly when true trade-offs are identified.