Align plans with domain models and update CONTEXT.md and ADRs.
npx skills add https://github.com/huangzida/skills --skill grill-with-docs-huangzida
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/huangzida/skills/tree/main/grill-with-docs Command: npx skills add https://github.com/huangzida/skills --skill grill-with-docs-huangzida
Grilling session that helps align your plan with the project's domain model, surface terminology gaps, and update documentation inline (CONTEXT.md, ADRs) as decisions crystallize.
Begin a guided interview with the project stakeholders to iteratively clarify decisions and update the repo docs as decisions crystallize.
High-intent search queries and answers about installing and using this skill.
To align your architecture plan with the domain model, run a guided grilling session that surfaces terminology gaps and resolves misalignments between your strategy and existing domain definitions. It iteratively clarifies decisions and updates documentation as your plan crystallizes.
You need to update CONTEXT.md and ADRs during planning when domain terminology shifts or new architectural decisions emerge. This ensures governance documentation stays synchronized with your evolving strategy, capturing clarifications and guiding future project discussions.
Uncover terminology gaps through a comprehensive interview process that questions project stakeholders about assumptions and dependencies. This grilling technique exposes misalignments between your plan and the project's domain language, ensuring consistency across documentation and code.
The best way to stress-test domain terminology decisions is applying a guided questioning framework during architecture sessions. It identifies misalignments with the domain model, captures crystallized decisions in ADRs, and updates CONTEXT.md to maintain governance and terminology consistency.
Yes, you can use this grilling session to clarify dependencies between architectural decisions. It guides comprehensive questioning to uncover hidden assumptions and relationships, ensuring that updates to CONTEXT.md and ADRs reflect the full context of your governance strategy.
Project documentation loses terminology consistency when domain language evolves without synchronized updates to CONTEXT.md and ADRs. A grilling session resolves this by iteratively clarifying terms, capturing decisions, and aligning documentation with the actual domain model.
chichexMaintain project domain models via CONTEXT.md glossary and ADR files.
ClyptAICompare project plans against domain models to surface terminology gaps.
iceflowerApply Domain-Driven Design patterns to model aggregates and bounded contexts.
KamiJeongAnalyze documentation collections for drift, coverage gaps, and broken cross-references.
