Stress-test product plans against domain glossary and documented decisions.
npx skills add https://github.com/imsus/cto --skill grill-with-docs-imsus
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/imsus/cto/tree/main/.agents/skills/grill-with-docs Command: npx skills add https://github.com/imsus/cto --skill grill-with-docs-imsus
It prevents misaligned plans and fuzzy terminology by forcing a shared understanding of the domain model and updating the project’s glossary and decision records as clarity emerges.
CONTEXT.md language and proposes canonical terms when users use vague or overloaded wording.CONTEXT.md inline when terms are resolved and offers ADRs only when a decision is hard to reverse, surprising without context, and involves real trade-offs.Use grill-with-docs to walk through your current plan step by step and refine it against the existing domain model and documentation.
High-intent search queries and answers about installing and using this skill.
To stress-test a product plan against a domain model, you interrogate design assumptions iteratively, checking terminology and concept boundaries against existing documentation to detect conflicts and harden the system design.
You should create an Architecture Decision Record when a design choice involves real trade-offs, is hard to reverse, or would be surprising without prior context, ensuring documented decisions are captured systematically.
To align project terminology, you compare newly proposed wording against existing CONTEXT.md language, detect vague or overloaded terms, and update the glossary inline with canonical terms as clarity emerges.
The best way to reconcile a design-tree walkthrough with codebase reality is through iterative single-question prompting, exploring the codebase on demand to resolve decision dependencies and verify implementation alignment.
Existing CONTEXT.md and ADR artifacts are required to effectively review a system plan, as they provide the prior domain glossary and documented decisions needed to detect conflicts and align terminology.
Detecting CONTEXT language conflicts improves documentation alignment by immediately identifying when user wording contradicts existing domain definitions, triggering inline updates to CONTEXT.md to maintain a shared understanding.
mpsuesserValidate implementation plans against repository glossary and documented decisions.
takuto277Guide structured interviews to validate project plans against domain models.
LeeSandersonInterrogate plans and designs through iterative questioning and decision tree traversal.
shushuznStress-test software plans against documented domain models and existing decisions.