What problem does it solve? Turning a design brief into an actionable build plan is error-prone: tasks end up too large, horizontally split (HTML then CSS then JS), or ordered without regard to dependencies and risk. This Skill reads a design brief and the existing codebase, then produces an ordered markdown checklist of small, independently verifiable vertical-slice tasks. ## Core Features & Use Cases - Brief and codebase analysis: Locates .design/*/DESIGN_BRIEF.md, information architecture, and token files, then scans existing components, pages, naming conventions, and dependencies to classify what gets reused, modified, or created. - Vertical-slice task breakdown: Each task bundles structure, styling, and interaction, is independently buildable, and is verifiable against the brief. - Dependency- and risk-aware ordering: Foundation and shared components come first, visually prominent and high-risk pieces are scheduled early, and the result is saved as TASKS.md in the feature's .design/<feature-slug>/ folder. - Use Case: After writing a design brief for a new dashboard page, ask for a task breakdown and receive a TASKS.md checklist grouped into Foundation, Core UI, Interactions & States, Responsive & Polish, and Review sections. ## Quick Start Ask the assistant to break the design brief in the .design folder into an ordered build task list and save it as TASKS.md.
