Align project plans with domain terminology and update CONTEXT.md and ADRs.
npx skills add https://github.com/yamcodes/arkenv --skill grill-with-docs-yamcodes
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/yamcodes/arkenv/tree/main/skills/grill-with-docs Command: npx skills add https://github.com/yamcodes/arkenv --skill grill-with-docs-yamcodes
Grills your plan against the repo's domain language, forcing alignment with the existing docs and decisions to prevent drift.
Initiate a grill-with-docs session to stress-test your plan against the repository's domain model and update CONTEXT.md and ADRs as decisions crystallize.
High-intent search queries and answers about installing and using this skill.
Aligning your project plan with domain terminology requires iteratively questioning assumptions and cross-referencing the existing domain model. This process enforces precise language updates to docs/CONTEXT.md and ADRs inline, preventing documentation drift by capturing decisions as they crystallize.
An ADR is an Architecture Decision Record that captures how and why specific technical choices are made. You need to update ADRs during software planning when decisions crystallize through iterative questioning, ensuring your repository maintains a coherent, discoverable record of decisions.
Surface hidden dependencies and assumptions by applying relentless questioning to every aspect of your plan against the repository's domain language. This guided exploration validates your terminology against existing documentation and forces misalignments into the open.
Validating terminology against an existing domain model is the core mechanism of this approach. It guides exploration of the codebase and existing documentation to enforce precise language, resolving misalignments between your plan and the project's established domain terms.
The best way to maintain CONTEXT.md files is through live, inline updates as decisions crystallize during planning sessions. This ensures the repository language stays current and produces a coherent record of how domain terminology and architectural decisions evolve.
You should avoid using ADRs for trivial or non-architectural decisions that do not impact the domain model. ADRs are intended to capture explicit, significant decisions through iterative alignment, ensuring a discoverable record without cluttering the repository with minor technical choices.
ThalfmanReview project plans for domain model alignment and terminology consistency.
ishandutta2007Capture shared domain language and architectural decisions in technical documentation.
roerohanValidate implementation plans against project domain models and architectural decisions.
AimeerrhythmVerify cross-file consistency across changed documents in multi-round review loops.
