brief-to-taskslisted

This skill turns a design brief into an ordered, buildable task list. Each task is a vertical slice: a piece of UI that can be built, reviewed, and verified on its own. ## Example prompts - "Break the brief into tasks" - "What should I build first?" - "Create a task list from the design brief" - "Plan the build order for this feature" ## Process 1. Read the design brief. Look for `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. Also check for `INFORMATION_ARCHITECTURE.md` and a tokens file in the same subfolder. If none exist, ask the user to describe what they are building. 2. Explore the existing codebase to understand what is already built. Scan specifically for: - **Component directories**: `components/`, `ui/`, `shared/` and list every component by name - **Existing pages/views**: what is already built that this feature must coexist with - **Token/theme files**: `tokens.css`, `globals.css`, Tailwind config, theme providers - **File naming conventions**: kebab-case, PascalCase, how files are organized (by feature, by type) - **Test files**: if tests exist alongside components, new tasks should include test expectations - **Package.json dependencies**: what UI libraries, animation libraries, and icon sets are already installed - Classify each relevant component as: will be reused as-is, needs modification, or does not exist yet. Only components that ne