brief-to-tasks
This skill transforms a design brief into a structured task list where each item is a vertical slice—a complete, self-contained piece of work that can be built and verified independently. It scans your codebase for existing components and tokens, then orders tasks by dependencies, visual priority, and risk to keep your build moving forward efficiently.
brief-to-tasks converts a design brief into an ordered checklist of independently buildable tasks using vertical slices.
AI-generated summary based on this skill's SKILL.md
Install
julianoczkowski/designer-skills/brief-to-tasks
git clone https://github.com/julianoczkowski/designer-skills
cp -r designer-skills/brief-to-tasks ~/.claude/skills/brief-to-tasksFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does brief-to-tasks break design brief into tasks?
brief-to-tasks transforms your design brief into a structured task list where each item is a vertical slice—a complete, self-contained piece of work that can be built and verified independently. The skill scans your codebase for existing components and tokens, then orders tasks by dependencies, visual priority, and risk to keep your build moving forward efficiently.
What does brief-to-tasks identify in a feature design?
brief-to-tasks identifies foundational, core, and polish tasks from your feature design. Foundational tasks establish the structural base, core tasks deliver primary functionality, and polish tasks refine the user experience. This layered approach ensures you build in the right sequence and can ship incrementally.
How does brief-to-tasks plan build order for a feature?
brief-to-tasks plans the optimal build sequence using vertical slices and dependency analysis. It examines which tasks must complete before others can start, weighs visual priority and implementation risk, and generates an ordered checklist with task descriptions and reuse/creation notes so you know exactly what to build first.
Can brief-to-tasks generate a markdown checklist?
Yes. brief-to-tasks generates a markdown checklist with task descriptions and reuse/creation notes. Each task includes context about whether components or tokens already exist in your codebase or need to be created, making it easy to track progress and avoid duplicate work.
What should I build first according to brief-to-tasks?
brief-to-tasks determines what to build first based on risk and visual priority. It analyzes your design brief to surface high-impact, low-risk tasks that unblock downstream work and establish confidence early. The result is an independently buildable task list ordered for maximum efficiency.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
-
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 forINFORMATION_ARCHITECTURE.mdand a tokens file in the same subfolder. If none exist, ask the user to describe what they are building. -
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
brief-to-tasks/SKILL.md