task-breakdown

Break down complex designs into epics, tasks, and dependencies.

734|197|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/jasonkneen/kiro --skill task-breakdown-jasonkneen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-breakdown
Source: https://github.com/jasonkneen/kiro/tree/main/skills/task-breakdown
Command: npx skills add https://github.com/jasonkneen/kiro --skill task-breakdown-jasonkneen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts technical designs into actionable, sequenced implementation tasks, enabling incremental progress and clear ownership across teams.

Core Features & Use Cases

  • Structured two-level task hierarchy (epics and tasks) to mirror design components and track progress.
  • Dependency-aware sequencing and prioritization to reveal blockers and optimize delivery.
  • Alignment with requirements and validation criteria to ensure traceability and quality.
  • Supports sprint planning, task estimation, and handoff between design, development, and QA.

Quick Start

Provide a design brief and receive a ready-to-use task breakdown with epics, tasks, and dependencies.

Frequently Asked Questions about task-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a design document into actionable development tasks?

To break down a design into development tasks, provide a design brief to generate a structured two-level hierarchy of epics and tasks. This creates a ready-to-use task breakdown with dependency-aware sequencing aligned to your requirements.

What is an epic and task hierarchy for incremental software delivery?

An epic and task hierarchy for incremental delivery maps design components to trackable units of work. It structures implementation into epics containing specific tasks, ensuring traceability to validation criteria and clear ownership across teams.

How do I sequence development tasks with dependencies for sprint planning?

Sequence development tasks with dependencies by applying dependency-aware prioritization to your task breakdown. This reveals blockers and optimizes incremental delivery, directly supporting sprint planning, task estimation, and team handoffs.

Can I map technical requirements to completion criteria for QA handoffs?

Yes, you can map technical requirements to completion criteria by aligning tasks with validation standards during breakdown. This ensures traceability and quality, supporting smooth handoffs between design, development, and QA teams.

What is the best way to structure a roadmap from a technical design brief?

The best way to structure a roadmap from a technical design is to generate a spec-driven task breakdown. This produces dependency-aware epics and tasks that satisfy clear objectives and provide a reusable template for planning.

Does task-breakdown work without external project management dependencies?

Yes, task-breakdown works without external project management dependencies. It operates as a standalone planning tool to convert technical designs into sequenced implementation tasks, requiring only a design brief as input.