What problem does it solve? Plans often contain fuzzy terminology, hidden contradictions with existing code, and undocumented decisions that future readers cannot understand. This Skill runs an interrogation-style session that challenges your plan against your project's domain language and documented decisions, capturing outcomes in CONTEXT.md and ADR files as they crystallise. ## Core Features & Use Cases - Relentless plan interrogation: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Domain language enforcement: Challenges terms that conflict with the existing CONTEXT.md glossary, sharpens vague wording into canonical terms, and updates the glossary inline. - Selective ADR creation: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: Before implementing a partial order cancellation feature, run a session to discover that your code cancels entire Orders while your plan assumes partial cancellation, then record the resolved terminology in CONTEXT.md and the trade-off in docs/adr/0003-partial-cancellation.md. ## Quick Start Start a grilling session to stress-test my implementation plan for the new billing flow against our existing domain model and documentation.
