Validate design plans against domain models using CONTEXT.md glossary alignment.
npx skills add https://github.com/Peiwvy/myskills --skill grill-with-docs-peiwvy
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/Peiwvy/myskills/tree/main/grill-with-docs Command: npx skills add https://github.com/Peiwvy/myskills --skill grill-with-docs-peiwvy
It helps you validate a proposed design by forcing alignment with your project’s existing domain glossary and documented decisions, reducing misunderstandings and “wrong terminology” drift.
Ask the AI to run the grilling session for your plan and update your CONTEXT.md and any necessary ADRs as you resolve the glossary and decision points.
High-intent search queries and answers about installing and using this skill.
To validate an architecture plan against a domain model, use a one-question-at-a-time interview to interrogate assumptions, reconcile terminology with CONTEXT.md, and clarify boundaries for integration decisions.
The best way to align fuzzy domain terminology is to challenge conflicting terms immediately against CONTEXT.md and propose precise canonical terminology, updating the glossary inline as decisions are resolved.
Glossary conflict handling during a codebase review works by interrogating design assumptions and immediately proposing precise canonical terminology when language is fuzzy or overloaded, ensuring alignment with CONTEXT.md.
You should create an ADR for architecture decisions only when hard-to-reverse trade-offs are genuinely surprising without context, offering updates sparingly to document rejected alternatives and relationship boundaries.
Yes, you can update CONTEXT.md inline while resolving domain modeling decisions, applying the specified glossary format to document canonical terminology as soon as conflicts are reconciled.
Domain modeling interrogation requires no external dependencies to clarify integration boundaries, relying solely on a one-question-at-a-time interview process to walk down each branch of the design tree and resolve decision dependencies.
matt-rileyElicit and record domain terms and ADR decisions during planning.
TrebuchetDynamicsAlign engineering plans with repository domain language and documented architecture.
mykcsStress-tests software design plans against repository domain glossary and documented decisions.
silvarojasdiegoarturo91Checks proposals for consistency with glossary-defined terms and logged decisions.
