What problem does it solve?
This Skill solves the frequent issue of implementation plans that conflict with your project's existing domain terminology, documented architectural decisions, and actual codebase structure, which leads to wasted rework, team misalignment, and code that fails to fit project conventions.
Core Features & Use Cases
- Relentless Plan Validation: Asks targeted, one-at-a-time questions about every aspect of your plan to resolve decision dependencies and catch misalignments before work begins.
- Domain Terminology Enforcement: Flags conflicting or vague terms against your project's CONTEXT.md glossary to ensure consistent, precise language across the team.
- Automated Documentation Sync: Updates CONTEXT.md inline as terms are resolved, and creates ADRs for high-impact, hard-to-reverse decisions to keep project documentation aligned with planning outcomes.
- Use Case: For example, if you are designing a new order cancellation feature, this Skill will challenge whether your definition of "cancellation" matches the existing glossary, verify if the code supports partial cancellations as you described, and create an ADR if the chosen approach involves a non-reversible trade-off.
Quick Start
Use the grill-with-docs skill to stress-test your new user authentication feature plan against the project's existing domain terms and documented decisions.