What problem does it solve? Turning a rough feature idea into a validated design document requires exploring the codebase, resolving ambiguities, and structuring requirements—work that is often skipped or done inconsistently. This Skill drives that process end to end and produces a design doc ready for pipeline kickoff. ## Core Features & Use Cases - Codebase-Grounded Exploration: Gathers context from issues, architecture files, and code search before asking clarifying questions that reference concrete files and functions. - Structured Design Documents: Writes .design/<slug>.md with requirements, mechanically testable acceptance criteria, architecture notes, and tracked open questions. - Interactive Iteration & Validation: Resolves open questions conversationally, validates document quality, stores the doc as a knowledge page, and initializes a pipeline state file for crosslink kickoff. - Use Case: A developer says "design batch retry logic for sync" and receives a validated design doc grounded in the actual sync module, with unresolved decisions flagged as open questions. ## Quick Start Ask the assistant to design a feature, for example: design a document for adding batch retry logic to the sync module.