What problem does it solve? Plans often embed fuzzy terminology and decisions that contradict a project's existing domain language or documented architecture. This Skill runs a structured interrogation of your plan, one question at a time, checking every term and decision against CONTEXT.md glossaries and ADRs so inconsistencies surface before implementation. ## Core Features & Use Cases - Relentless plan interrogation: Walks each branch of the design tree, asking one question at a time with a recommended answer, and explores the codebase directly when a question can be answered there. - Terminology sharpening: Challenges terms that conflict with CONTEXT.md, proposes canonical names for vague language, and updates the glossary inline as terms are resolved. - Decision recording: Offers to write ADRs only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using the format in ADR-FORMAT.md. - Use Case: Before building a partial order cancellation feature, run a grilling session to discover that your code cancels entire Orders while your plan assumes partial cancellation, then record the resolution in CONTEXT.md and an ADR. ## Quick Start Start a grilling session on my plan for the new billing flow and challenge it against our existing CONTEXT.md and ADRs.
