grill-with-docs

Stress-testing a plan against domain documentation involves interrogating your proposed architecture against the repository's CONTEXT.md glossary and existing ADRs. The skill breaks the design into single questions, resolving dependencies and updating documentation inline as terminology conflicts are clarified.

An Architecture Decision Record is needed when a design trade-off is meaningful, surprising, and hard to reverse. The skill evaluates your proposed plan during interrogation and offers ADR creation only for trade-offs that meet these specific criteria, keeping documentation lightweight otherwise.

To disambiguate conflicting domain terminology, the skill cross-checks vague or conflicting terms against the project's CONTEXT.md file and proposes canonical wording. It inspects the codebase when needed to ensure terminology precision and relationship boundaries align with actual implementations.

Yes, you can update CONTEXT.md inline while resolving architecture decisions. The skill applies glossary and terminology updates directly to CONTEXT.md using a prescribed format as terms are clarified during the guided interrogation process.

A limitation of glossary alignment for architecture reviews is that it requires guided, single-question feedback-waiting interrogation, meaning it cannot process decisions asynchronously. It also relies entirely on the accuracy of existing CONTEXT.md and ADR documentation to validate proposed plans.