task-breakdown-phase

What problem does it solve?

This Skill transforms large, unmanageable feature requirements into small, actionable tasks with clear completion criteria, preventing ambiguity and enabling agile development.

Core Features & Use Cases

• Right-Sized Tasks: Breaks down work into tasks typically 0.5-1 day (4-8 hours) in duration, making them easier to estimate and track.
• TDD-First Sequencing: Organizes tasks to follow a Test-Driven Development (TDD) workflow, ensuring tests are written before implementation.
• Clear Acceptance Criteria: Defines 2-4 specific, measurable, and testable acceptance criteria for each task, leaving no doubt about "done."
• Use Case: Take an implementation plan for a "Student Progress Dashboard" and break it down into 20-30 granular tasks. This includes creating database migrations, writing unit tests for a service, implementing the service, writing integration tests for an API, and implementing UI components, all sequenced by dependencies.

Quick Start

Example of a right-sized task with clear acceptance criteria

Task N: Create Database Migration for Time Logs

Complexity: Low (2-4 hours)

Description: Create Alembic migration to add time_logs table with student_id, lesson_id, time_spent fields.

Acceptance criteria:

• [ ] Migration runs successfully on clean database
• [ ] Foreign keys enforce referential integrity
• [ ] Rollback works without errors