brief-to-taskslisted

This skill turns a design into an ordered, buildable task list, written into the `## Tasks` section of the feature's `.design/YYYY-MM-DD-<slug>.md`. 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. Find the feature's design file by the procedure in `${CLAUDE_SKILL_DIR}/../design/SKILL.md` → **Finding the design file**. Read every section already filled — `## Problem`, `## Solution`, `## Scope` (or the PRD it points at), `## Experience` and its `### Tokens`, `## Architecture`, `## Structure`, `## Tests`. The cases in `## Tests` become test tasks alongside the implementation work: one task per meaningful assertion, grouped in the "Tests" group below. In a legacy six-file folder, read `DESIGN_BRIEF.md` / `INFORMATION_ARCHITECTURE.md` / `DESIGN_TOKENS.md` / `TEST_PLAN.md` and write `TASKS.md` beside them as before. If nothing exists, 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, th