What problem does it solve?
Software plans often drift from existing domain terminology, documented architectural decisions, and established domain models, leading to costly rework, team confusion, and documentation that no longer reflects the actual system design.
Core Features & Use Cases
- Domain Alignment Checks: Challenges your plan against existing project glossaries (CONTEXT.md) and architectural decision records (ADRs) to catch terminology conflicts and misalignment with past decisions.
- Terminology Sharpening: Identifies vague or overloaded terms in your plan and proposes precise, consistent canonical terms to align with your project's domain language.
- Inline Documentation Updates: Updates CONTEXT.md and creates new ADRs in real time as decisions are finalized, ensuring documentation stays synchronized with your planning process.
- Use Case: For example, if you are planning a new subscription cancellation feature, the skill will flag if you use "cancel" to refer to both one-time order cancellations and recurring subscription cancellations when your CONTEXT.md defines those as distinct concepts, and prompt you to create an ADR if the cancellation logic is hard to reverse and involves a meaningful trade-off.
Quick Start
Use the grill-with-docs skill to walk through your new payment processing plan, challenge it against the project's existing domain glossary and ADRs, and update documentation inline as you resolve terminology conflicts and finalize key decisions.
