What problem does it solve? Teams often jump straight into coding features without clarifying intent, requirements, or design, which leads to rework and misaligned implementations. This Skill enforces a structured dialogue that classifies each request, explores the problem space, and requires explicit human approval before any code is written. ## Core Features & Use Cases - Three-Path Classification: Routes every request into spike, bounded, or architectural tracks so the process depth matches the task's actual complexity. - Approval Gates: Blocks implementation until the human partner explicitly approves the presented design, with a hard gate that applies to every task size. - Spec Authoring and Review: Writes validated design documents to dated spec files, runs a self-review for placeholders and contradictions, and hands off to implementation planning. - Visual Companion Server: Ships a local browser companion (Node.js server, WebSocket updates, session-key authentication) for showing mockups, diagrams, and layout options during design discussions. - Use Case: When asked to add a new subsystem, the Skill explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, writes a committed design spec, and only then invokes the writing-plans skill. ## Quick Start Ask the agent to brainstorm the design for a new feature before writing any code, and it will classify the request and walk you through questions and a design proposal.
