1. Habit
  2. Skills
  3. Brief to Tasks skill
julianoczkowski · 5K installs

Brief to Tasks skill
Runs by itself, a brief is written.

Turn design briefs into buildable tasks.

Install the Brief to Tasks skill and make it a habit: follow https://gethabit.dev/skills/julianoczkowski/brief-to-tasks.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

5K installs589 starsApache-2.0 licenceSource on GitHub ↗

Brief to Tasks

by julianoczkowski · 5K installs

The skill

The brief to tasks skill breaks a design brief into an ordered checklist of independently buildable vertical slices, based on the existing codebase, and saves it as TASKS.md next to the brief.

Only when you ask.

The habit

Turn design briefs into buildable tasks.

↻ Runs by itselfa brief is written

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

a brief is written. Runs in Claude Code routine.

  • ↻ a brief is written
  • a new or changed .design/*/DESIGN_BRIEF.md

02

It checks its work

task list saved, valid. If a check fails, it tries again.

  • ✓TASKS.md exists in the brief's .design/<feature-slug>/ folder
  • ✓every task says it reuses, modifies or creates components
  • ✓no task is only project setup
  • ✓the list ends with a design review task

03

It remembers

TASKS.md checklist. The next run reads it first: the brief and existing task checklist.

.design/<feature-slug>/TASKS.md

One run, step by step.
Then it stops.

Stop ruleStops after one brief and one revision.

  1. 01

    Read the brief

    Your agent reads the newest DESIGN_BRIEF.md, plus INFORMATION_ARCHITECTURE.md and tokens if present.

  2. 02

    Scan the codebase

    It lists components, pages, theme files, naming rules, tests and dependencies.

  3. 03

    Classify components

    It marks each as reused, modified or new.

  4. 04

    Slice the work

    It writes tasks that each cover structure, styling and interaction.

  5. 05

    Order tasks

    It puts dependencies, the most visible element and the riskiest piece first.

  6. 06

    Save

    It writes TASKS.md from the template, ending with a /design-review task.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Brief to Tasks skill helps.

Use it when

  • ✓ You have a finished design brief
  • ✓ You need a build order
  • ✓ You want tasks that reuse existing components

Skip it when

  • – You have no brief or clear idea yet
  • – The work is a single tiny fix

Questions

Brief to Tasks skill, answered.

What if there is no brief?

It asks you to describe what you are building.

How deep can tasks nest?

One level at most; flat lists are easier to work through.

How do I install the Brief to Tasks skill?

Copy the prompt at the top into your agent. It installs the skill from julianoczkowski/designer-skills and sets up the habit. Or run npx skills add julianoczkowski/designer-skills --skill brief-to-tasks.

Is the Brief to Tasks skill free?

Yes. It is published under Apache-2.0. Habit is free too.

Brief to Tasks. Now as a habit.

Install the Brief to Tasks skill and make it a habit: follow https://gethabit.dev/skills/julianoczkowski/brief-to-tasks.md

  • Free
  • No account
  • Undo in one line

All julianoczkowski skills →More planning skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by julianoczkowski, published under Apache-2.0. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.