Stress-tests software design plans against repository domain glossary and documented decisions.
npx skills add https://github.com/mykcs/myk-skills --skill grill-with-docs-mykcs
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/mykcs/myk-skills/tree/main/grill-with-docs Command: npx skills add https://github.com/mykcs/myk-skills --skill grill-with-docs-mykcs
It prevents “hand-wavy” design plans by forcing a shared understanding of your project’s domain language and decisions, then updating CONTEXT.md and ADRs as the reasoning solidifies.
Use grill-with-docs to stress-test the current plan by saying: "Run grill-with-docs on my design plan for this repo, asking questions one at a time and updating CONTEXT.md and ADRs only when justified."
High-intent search queries and answers about installing and using this skill.
To stress-test a software design plan against existing domain terminology, walk through the design tree one question at a time, cross-checking answers against your repository's documented glossary and source code to clarify trade-offs before implementation.
Aligning an architecture review with a CONTEXT.md glossary requires step-by-step questioning that detects term conflicts, enforces canonical terminology definitions, and updates documentation inline as domain concepts are clarified.
Write an Architecture Decision Record during codebase exploration only when a resolved design decision demonstrates meaningful irreversibility, surprise, and trade-offs, ensuring the documented outcome captures significant architectural constraints.
Domain modeling prevents hand-wavy integration planning across multiple branches by probing edge cases with concrete scenarios, forcing precise relationship boundaries, and resolving terminology conflicts against the repository's source of truth.
Update domain documentation inline while clarifying software design boundaries by resolving terminology conflicts during the interview process, immediately writing canonical definitions into CONTEXT.md, and cross-checking claims against the codebase.
shushuznStress-test software plans against documented domain models and existing decisions.
askferretGenerate MADR-format ADRs, arc42 documentation, and plan-context.md files.
babuallyChallenge proposed plans against codebase terminology and documented ADR decisions.
akillnessValidate architecture plans against project domain language in CONTEXT.md and ADRs.
