Validate a development plan against domain glossary and documented decisions.
npx skills add https://github.com/gbencke/dotfiles --skill grill-with-docs-gbencke
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/gbencke/dotfiles/tree/main/pi/skills/grill-with-docs Command: npx skills add https://github.com/gbencke/dotfiles --skill grill-with-docs-gbencke
It prevents misunderstandings by forcing your plan to match the project’s existing domain language and documented decisions, so your approach stays coherent as it evolves.
Tell the AI: “Grill my plan until we agree on the domain model terms and resulting decisions, updating CONTEXT.md and proposing ADRs only when appropriate.”
High-intent search queries and answers about installing and using this skill.
To prevent terminology drift, stress-test your proposed domain model plan against an existing project glossary and documented decisions. This process catches mismatches immediately, ensuring your approach stays coherent with shared concepts before implementation begins.
The best way to clarify ambiguous design tradeoffs is through an iterative question-by-question interview that probes edge cases with concrete scenarios. This step-by-step process makes dependencies between decisions unambiguous before you finalize documentation.
Validate development requirements by cross-checking your claims against the existing repository to surface contradictions. This codebase review verifies that proposed plans align with what the code actually does and with documented decisions.
Propose an ADR only when a design decision meaningfully trades off options and would be hard to reverse. This ensures your ADR creation focuses on significant architectural choices rather than routine documentation updates to CONTEXT.md.
Updating CONTEXT.md requires resolving glossary conflicts first, as the process aligns terminology through relentless domain interrogation. Inline updates happen only after shared concepts are clarified and design choices depend on agreed domain definitions.
matt-rileyElicit and record domain terms and ADR decisions during planning.
IsKenKenYaValidate proposed plans against CONTEXT.md domain models and ADRs.
a35506322Stress-test project plans against domain documentation, codebase, and ADRs.
oaustegardIdentify ambiguous user requests and ask targeted clarifying questions.
