Interrogate a design plan against the repository domain model in CONTEXT.md.
npx skills add https://github.com/koseki2580/skills --skill grill-with-docs-koseki2580
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/koseki2580/skills/tree/main/skills/grill-with-docs Command: npx skills add https://github.com/koseki2580/skills --skill grill-with-docs-koseki2580
It prevents ambiguous, mismatched implementations by forcing you to reconcile your plan with the existing domain glossary, update terminology as you learn, and document decisions as they crystallize.
Use grill-with-docs for your next design or implementation plan to pressure-test vocabulary and domain relationships against CONTEXT.md while the AI asks one question at a time until you align.
High-intent search queries and answers about installing and using this skill.
To align your software design plan with a domain glossary, this Skill interrogates your plan branch-by-branch against CONTEXT.md to resolve terminology conflicts and propose canonical replacements, updating the glossary immediately as you answer questions one at a time.
Documenting architecture decisions during a design session is handled by generating Architecture Decision Records (ADRs) using specified formats, offered only when trade-offs make it worthwhile, while keeping CONTEXT.md updated as terms are resolved inline.
Yes, interrogating a codebase plan requires YAML frontmatter metadata to function, ensuring that domain boundaries and decision dependencies are resolved correctly while cross-referencing existing code and documentation.
You eliminate ambiguous assumptions in multi-step implementation plans by applying relentless plan interrogation that interviews the plan branch-by-branch, resolving dependencies between decisions one-by-one until shared understanding is reached.
You should not use this one-question-at-a-time domain modeling approach for simple tasks that lack multi-step architecture needs, as it requires waiting for feedback and is built for sessions where terminology, boundaries, and decision dependencies must be resolved.
matt-rileyElicit and record domain terms and ADR decisions during planning.
voidrotDevelop domain terminology and maintain Architecture Decision Records (ADRs).
LumenYoungStress-test plans against domain models and documented decisions.
amazingloft999-droidInterrogate product plans against the domain model and update CONTEXT.md and ADRs.
