What problem does it solve? Plans often embed fuzzy terminology and undocumented trade-offs that later confuse teams. This Skill stress-tests a plan through relentless one-at-a-time questioning, challenges it against the project's existing domain language, and captures resolved terms and decisions as living documentation. ## Core Features & Use Cases - Socratic 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. - Ubiquitous language enforcement: Challenges terms that conflict with CONTEXT.md, sharpens vague wording into canonical terms, and updates the glossary inline as terms are resolved. - Decision capture via ADRs: Offers to write numbered ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: While planning a partial order cancellation feature, the Skill notices the code cancels entire Orders, surfaces the contradiction, resolves the term 'cancellation' into CONTEXT.md, and records the chosen approach as ADR 0003. ## Quick Start Ask the assistant to grill you on your implementation plan for a new feature and update the project's CONTEXT.md and ADRs as decisions are made.
