Step 3 Breakdown

Step 3 · Breakdown

/breakdown decomposes approved work into small, ordered tasks that can be implemented and reviewed without hidden scope creep.

Field	Value
Command	/breakdown [design or requirements]
Habit	H3 Put First Things First
Previous	Step 2 · Design
Next	Step 4 · Build Brief

Use This When

• The work spans multiple files or phases.
• Tasks need dependencies, sequencing, or parallelization decisions.
• You want to separate required work from optional ideas.

Skip When

• The change is a single, obvious edit.
• A reviewed task list already exists and is still current.

Output

• Atomic tasks.
• Dependencies and ordering.
• Priority by importance, not novelty.
• Explicit exclusions for out-of-scope work.
• Suggested validation per task.

Handoff

/build-brief should receive one task at a time, with dependencies and expected validation clear.

See Also

• Workflow Overview
• Step 4 · Build Brief
• Habits Reference
• Source skill