Validate proposed plans against CONTEXT.md domain models and ADRs.
npx skills add https://github.com/IsKenKenYa/Commory --skill grill-with-docs-iskenkenya
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/IsKenKenYa/Commory/tree/main/.windsurf/skills/grill-with-docs Command: npx skills add https://github.com/IsKenKenYa/Commory --skill grill-with-docs-iskenkenya
It prevents misalignment between a proposed design and the project’s established terminology, domain model, and documented decisions by forcing a plan to be clarified and validated.
Ask the AI to run grill-with-docs on your proposed change, and provide the high-level plan you want stress-tested.
High-intent search queries and answers about installing and using this skill.
To validate an architecture plan against existing documentation, you stress-test the proposed design by cross-referencing the codebase and questioning every branch against the established domain model to eliminate ambiguity.
Resolving mismatched terminology in a domain model requires detecting conflicts within the project glossary, proposing precise canonical terms, and immediately updating CONTEXT.md to maintain consistency across the architecture.
You need an Architecture Decision Record when your design stress-testing reveals a hard-to-reverse trade-off. ADRs should be suggested sparingly to ensure decision traceability only for significant architectural choices, not implementation details.
Testing edge cases for ambiguous domain boundaries involves using scenario-driven boundary testing, probing relationships with concrete invented scenarios to resolve ambiguities and validate the architecture step-by-step.
Yes, you can use CONTEXT.md to track glossary updates during a codebase review. It should be updated inline with resolved terms immediately, keeping the documentation free of implementation details and aligned with the domain model.
A proposed integration plan conflicts with documented architecture decisions when terminology is mismatched or boundaries are ambiguous. Relentless plan interviewing and codebase cross-referencing surface these contradictions to reconcile statements with reality.
acme-skunkworksValidate project plans against domain models and update CONTEXT.md and ADRs.
OrestesKStress-test implementation plans against codebase, domain terminology, and architectural decisions.
JohnRobert-OlanoMap codebase modules and their interconnections for high-level review.
majiayu000Analyze codebases for redundant design patterns and generate step-by-step refactoring plans.
