What problem does it solve? Teams often jump straight into coding vague feature requests, leading to wrong architectural choices, scope creep, and costly rework. This Skill enforces a structured exploration phase that surfaces hidden assumptions and decision points before any code is written. ## Core Features & Use Cases - Socratic Questioning Protocol: Generates prioritized questions (blocking, high-leverage, nice-to-have) that reveal architectural consequences rather than just gathering data. - Tradeoff Analysis Tables: Compares 3+ distinct approaches across dimensions like cost, latency, complexity, and maintenance burden. - Lateral Expansion: Introduces edge cases and adjacent features users haven't considered, such as timezone handling or offline capability. - Use Case: When a user says "build an Instagram clone," the Skill produces decision questions on photo storage strategy, feed algorithms, and authentication methods with concrete tradeoff tables instead of premature boilerplate code. ## Quick Start Ask the assistant to brainstorm architectural options and tradeoffs for your new feature idea before writing any code.