grill-with-docs

To validate feature plans against domain documentation, cross-reference your design choices with existing CONTEXT.md glossary terms and ADRs. This catches terminology mismatches and contradictions with documented architectural decisions to prevent rework and misalignment.

Domain terminology alignment ensures consistent language across a project by cross-referencing new plans against existing CONTEXT.md glossary terms. It identifies vague or overloaded terms and proposes precise, project-aligned alternatives to maintain shared understanding.

You can keep CONTEXT.md and ADRs updated during planning sessions by using inline documentation updates. As decisions are finalized, the documentation is updated in real time to stay in sync with planning progress.

You need to stress-test plans against domain docs when designing features that might conflict with established domain rules or architectural decisions. This avoids building features that contradict existing terminology, which leads to wasted engineering effort.

Yes, you can catch terminology contradictions in your software planning workflow by automatically cross-referencing your plan against existing project glossaries. It flags mismatches, such as using a term differently than the documented definition.

Plan validation is most effective with existing ADRs and a CONTEXT.md glossary. Without them, the Skill lacks the project-specific context needed to catch contradictions, enforce consistent domain language, and align design choices.