What problem does it solve? Jumping straight into code without a validated design leads to rework, unexamined assumptions, and misaligned features. This Skill enforces a structured dialogue that turns rough ideas into reviewed, approved design specs before any implementation begins. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents the design in sections for incremental approval. - Spec Document Generation: Writes the validated design to docs/superpowers/specs/, runs a self-review for placeholders, contradictions, and ambiguity, then hands off to the writing-plans skill. - Visual Companion: Optionally serves browser-based mockups, diagrams, and A/B layout comparisons via a local WebSocket server, recording user clicks as structured events. - Use Case: Before building a new feature, use this Skill to refine requirements, compare architectural approaches, and produce a committed design document that the user has explicitly approved. ## Quick Start Ask the agent to brainstorm the design for a new feature before writing any code, and answer its clarifying questions one at a time.