What problem does it solve? Plans often contain fuzzy terminology, hidden contradictions with existing code, and undocumented decisions that future engineers will question. This Skill runs a relentless one-question-at-a-time interview that challenges your plan against your project's domain language and codebase, then captures resolved terms and decisions as documentation inline. ## Core Features & Use Cases - Socratic plan interrogation: Walks each branch of the design tree one question at a time, providing a recommended answer for every question and exploring the codebase when answers can be found there. - Ubiquitous language enforcement: Challenges terms that conflict with the existing CONTEXT.md glossary, sharpens vague words into canonical terms, and updates the glossary inline as terms are resolved. - Selective ADR capture: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal one-paragraph format. - Use Case: Before implementing a partial order cancellation feature, run a grilling session that exposes the contradiction between your stated behavior and the code's full-cancellation logic, resolves 'cancellation' vs 'refund' terminology into CONTEXT.md, and records the event-sourcing decision as ADR 0003. ## Quick Start Start a grilling session on my plan for the new billing flow and update our CONTEXT.md and ADRs as we make decisions.
