What problem does it solve? It turns a clarified feature requirement into a single authoritative design document ({slug}-design.md) plus an actionable checklist ({slug}-checklist.yaml), so that downstream implementation and acceptance phases have one consistent, reviewable source of truth instead of scattered conversation history. ## Core Features & Use Cases - Structured design drafting: Produces a design doc covering terminology, decisions and constraints, noun-layer (entities/contracts) and orchestration-layer (workflows) changes in a current-state-to-change format, mount-point inventory, and acceptance contracts. - Multiple entry modes: Supports formal drafting from a clarified requirement, an initialization mode that scaffolds a feature directory with an empty intent draft, and starting from a roadmap item with automatic status write-back to items.yaml. - Structural health check: Includes a mandatory section evaluating whether files about to be modified are oversized or mixed-responsibility, deciding on a behavior-preserving micro-refactor before implementation. - Use Case: A developer says "write a design doc for the export-csv feature"; the skill checks for existing intent/brainstorm docs, reads architecture and related code, drafts the full design, iterates through review, then emits a validated checklist YAML. ## Quick Start Tell the assistant to start the design phase for your clarified feature, for example by saying "start the design plan for user-auth" once you know what to build, for whom, and how success is measured.
