Validate plans against repository documentation and update CONTEXT.md and ADRs.
npx skills add https://github.com/govoel/voel --skill grill-with-docs-govoel
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/govoel/voel/tree/main/.agents/skills/grill-with-docs Command: npx skills add https://github.com/govoel/voel --skill grill-with-docs-govoel
This Skill helps teams stress-test their product plan against the repository's existing domain documentation and decisions, surfacing gaps in terminology and alignment.
Provide your plan and let me challenge its terminology and decisions against the repository's CONTEXT.md and ADRs to reach a shared, up-to-date model.
High-intent search queries and answers about installing and using this skill.
To validate domain terminology, you stress-test your product plan against the repository's CONTEXT.md and ADRs. This surfaces terminology gaps and aligns new design decisions with your current domain model.
You need to update ADRs and CONTEXT.md when architecture discussions or domain modeling decisions diverge from your current documentation. This ensures changes remain consistent, accurate, and traceable in project history.
Yes, you can harmonize glossary terms across single-context repositories by validating definitions during design discussions. This inline approach ensures your context maps and knowledge graphs remain accurate as decisions crystallize.
The best way to trace binding decisions in documentation governance is to challenge your plan against existing ADRs. This identifies decision boundaries and prompts inline updates to keep your knowledge base traceable.
Yes, stress-testing plans works for domain modeling discussions by applying terminology checks against project documentation. It facilitates structured dialogue that yields a shared, up-to-date knowledge base across the repository.
rnaarlaValidate project plans against CONTEXT.md and ADRs for terminology consistency.
kenlckDebate design decisions against CONTEXT.md and ADR documentation.
Zangetsu101Define context-specific terminology and architectural decision records for your domain model.
OutlineDrivenExtract domain terms from dialogue and persist a canonical glossary to UBIQUITOUS_LANGUAGE.md.
