What is vertical slicing in this context?

Vertical slicing means every task card must connect the database, API, and UI layers together in a single loop, rather than separating backend and frontend work into different tasks.

Can I use this skill for general code optimization?

No, this skill intentionally bans vague terms like 'optimize' or 'improve.' It is designed solely for creating demonstrable, functional increments of code.

How small are the tasks generated by this skill?

Tasks are strictly limited to a maximum of one route, one page, or one domain model, ensuring they can be implemented and verified in a single AI turn.

What does the Definition of Done (DoD) include?

The DoD requires a functional UI entry point, data persistence, traceable logs, at least three unit tests, and clear README commands for execution.

Task Breakdown & Slicing

Name: Task Breakdown & Slicing
Author: ttmouse

byttmouse

•

Productividad y Flujo de Trabajo

Decomposes complex development requirements into independent, demonstrable vertical slices that can be implemented and verified in a single turn.

Acerca de

Task Breakdown is a specialized workflow skill for Claude Code designed to transform broad feature requests into atomic, executable task cards. Following a strict 'DB→API→UI' vertical slicing methodology, it ensures every task is a complete functional loop that can be demonstrated in under 60 seconds. By enforcing constraints like single data changes and minimal scope—limited to one route, page, or model—it eliminates ambiguity and provides a clear Definition of Done (DoD) for rapid, error-free development cycles.

Características Principales

Single Data Change enforcement (Create, Update, or Delete only)
Anti-vague terminology filter to ensure actionable results
25 GitHub stars
Vertical Slicing (DB to UI integration in every task card)
Granularity control (Max 1 route/page/model per task)
Strict Definition of Done (DoD) with verification instructions

Casos de Uso

Standardizing team task management within a repository using a unified TODO format.
Converting a complex monolithic requirement into small, manageable pull requests.
Planning a new software feature by defining its minimum viable execution steps.

Acerca de

Características Principales

Single Data Change enforcement (Create, Update, or Delete only)
Anti-vague terminology filter to ensure actionable results
25 GitHub stars
Vertical Slicing (DB to UI integration in every task card)
Granularity control (Max 1 route/page/model per task)
Strict Definition of Done (DoD) with verification instructions

Casos de Uso

Standardizing team task management within a repository using a unified TODO format.
Converting a complex monolithic requirement into small, manageable pull requests.
Planning a new software feature by defining its minimum viable execution steps.