What problem does it solve? Plans often embed fuzzy terminology and undocumented trade-offs that later confuse teams or get silently reversed. This Skill runs a structured interrogation of your plan against your project's existing domain language and documented decisions, capturing resolved terms and hard-to-reverse choices as documentation while the discussion happens. ## Core Features & Use Cases - Socratic plan review: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Terminology enforcement: Challenges terms that conflict with the project glossary in CONTEXT.md, sharpens vague language into canonical terms, and updates the glossary inline as terms are resolved. - Decision recording: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using sequential numbering in docs/adr/. - Use Case: Before implementing a new billing feature, run a grilling session to reconcile your plan with the existing CONTEXT.md definitions of Invoice and Customer, then capture the decision to use domain events instead of synchronous HTTP as ADR 0003. ## Quick Start Ask the assistant to grill your implementation plan for a new feature against the project's CONTEXT.md and existing ADRs before writing any code.
