What problem does it solve?
This Skill solves the problem of building plans that conflict with your project's existing domain language, documented architectural decisions, and established context, which leads to rework, miscommunication, and avoidable technical debt.
Core Features & Use Cases
- Plan Stress-Testing: Relentlessly interviews you about every aspect of your design to uncover gaps, contradictions, and unaddressed dependencies before implementation starts.
- Terminology Alignment: Challenges vague or conflicting terms against your project's existing CONTEXT.md glossary to ensure consistent, unambiguous language across the team.
- Inline Documentation Updates: Creates or updates ADRs and CONTEXT.md entries in real time as decisions crystallize, so documentation stays in sync with your planning process.
- Codebase Cross-Checking: Verifies that your planned behavior matches existing code implementation, surfacing contradictions early.
- Use Case: For example, if you are designing a new order cancellation feature, this Skill will confirm your definition of "cancellation" aligns with the project glossary, check if the codebase already supports partial cancellations, and prompt you to document the decision as an ADR if it involves irreversible trade-offs between customer experience and operational overhead.
Quick Start
Use the grill-with-docs skill to stress-test my plan for adding a user profile editing feature against our existing domain documentation and codebase.