What problem does it solve? Teams and agents often jump straight into coding on unexamined assumptions, producing wasted work and misaligned features. This Skill enforces a design-first gate: it explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and requires explicit user approval of a written design before any implementation begins. ## Core Features & Use Cases - Structured requirements dialogue: Explores existing files, docs, and commits first, then asks one question per message with a recommended answer, covering purpose, constraints, and success criteria. - Design approval gate: Presents the design section by section (architecture, components, data flow, error handling, testing), persists it to OpenSpec changes or a single Beads issue, runs a spec self-review, and blocks implementation until the user approves. - Visual companion server: Ships a Node.js WebSocket server (scripts/server.cjs) that serves HTML mockups, wireframes, and A/B option screens to a browser so visual questions can be answered by clicking instead of reading. - Use Case: Before building a new dashboard feature, the agent checks the repo, asks whether real-time updates are required, proposes polling versus WebSocket approaches, presents the design in sections, and only hands off to the implementation workflow after you approve the written spec. ## Quick Start Ask the agent to brainstorm and design the feature you have in mind before writing any code, and answer its clarifying questions one at a time until it presents a design for your approval.
