task-breakdown_skill

This skill converts designs into actionable, sequenced development tasks with clear objectives, dependencies, and measurable completion criteria.

TypeScript

492

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jasonkneen/kiro --skill task-breakdown

SKILL.md10.0 KB

Overview

This skill converts technical designs into actionable, sequenced implementation tasks that developers can pick up and complete incrementally. It produces a two-level task hierarchy, explicit dependencies, and clear completion criteria so teams can plan sprints, coordinate work, and validate progress. The output favors 2–4 hour task scopes and includes testing and integration steps.

How this skill works

The skill inspects a technical design and extracts implementation components: data models, services, API endpoints, UI components, tests, and integration points. It maps technical and logical dependencies, sequences tasks using one of several strategies (foundation-first, feature-slice, risk-first, or hybrid), and emits structured task entries with files, objectives, requirements references, and completion criteria. Tasks are sized for focused work and include testing obligations to ensure incremental validation.

When to use it

After design phase is approved and ready for implementation
When coordinating work across multiple developers or teams
During sprint planning or backlog refinement
To create an executable roadmap for an MVP or feature set
When you need to minimize blockers and enable parallel work

Best practices

Keep tasks focused: 2–4 hours of work per task
Specify files, functions, and tests for every task
Reference requirements and acceptance criteria explicitly
Sequence tasks to respect technical and logical dependencies
Include tests and integration steps as part of each task

Example use cases

Create a sequenced plan to implement user authentication with models, services, endpoints, and tests
Break a large feature into vertical feature-slices so one dev can deliver an end-to-end piece
Prioritize and schedule risky integrations early to reduce uncertainty
Prepare sprint-ready tasks for a cross-functional team with clear ownership and completion criteria
Refactor a legacy area by extracting interfaces first, then incrementally replacing implementations

FAQ

Aim for tasks that can be completed in 2–4 hours by a single developer; if a task takes longer, split it into sub-tasks with clear dependencies.

Which sequencing strategy should I pick?

Use foundation-first for new or complex systems, feature-slice for MVPs and fast validation, risk-first when uncertainty is high, or a hybrid approach to balance speed and stability.

How do you handle circular dependencies?

Extract interfaces first (IService patterns), implement concrete services against those interfaces, then wire with dependency injection to break cycles.

What testing should be included in each task?

Include unit tests for models/services, integration tests for API endpoints, and end-to-end tests for full feature slices; list the specific tests in the task description.