Task Breakdown and Dispatch

Decompose tasks into subtasks and dispatch them to AI team roles.

2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Burburton/amazingteam --skill task-breakdown-and-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Task Breakdown and Dispatch
Source: https://github.com/Burburton/amazingteam/tree/main/.ai-team/skills/task-breakdown-and-dispatch
Command: npx skills add https://github.com/Burburton/amazingteam --skill task-breakdown-and-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the process of breaking down large tasks into manageable subtasks and assigning them to the appropriate team roles, ensuring clarity and efficient workflow.

Core Features & Use Cases

  • Task Decomposition: Systematically breaks down complex tasks into logical phases and subtasks.
  • Role Assignment: Intelligently assigns subtasks to relevant AI roles (Architect, Developer, QA, etc.).
  • Dependency Management: Maps and visualizes dependencies between subtasks to identify critical paths and parallelizable work.
  • Task Manifest Generation: Creates a task.yaml file detailing subtasks, statuses, and acceptance criteria.
  • Workflow Coordination: Facilitates smooth handoffs and tracks progress through a defined state machine.
  • Use Case: When a new feature request comes in, this skill can automatically break it down into design, implementation, and testing subtasks, assigning each to the correct AI agent.

Quick Start

Use the Task Breakdown and Dispatch skill to decompose the new feature request described in the attached document.

Frequently Asked Questions about Task Breakdown and Dispatch

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

FAQPage Schema
How do I break down complex feature requests into actionable subtasks for an AI team?

Task breakdown systematically decomposes feature requests into logical phases and subtasks, assigning each to appropriate AI roles like Architect or Developer. It manages dependencies and generates a task manifest for workflow coordination.

Can I map task dependencies to identify parallelizable work for project planning?

Dependency mapping visualizes relationships between subtasks to identify critical paths and parallelizable work. This ensures smooth handoffs and tracks progress through a defined state machine for efficient workflow automation.

What is the best way to assign subtasks to specific AI roles for bug resolution and feature development?

Intelligent role assignment dispatches subtasks to relevant AI roles such as Architect, Developer, or QA. It supports feature development, bug resolution, refactoring, documentation, and CI failure analysis by defining deliverables and estimating effort.

How does generating a task manifest help with workflow automation and project planning?

Generating a task manifest creates a task.yaml file detailing subtasks, statuses, and acceptance criteria. This manifest facilitates workflow coordination by providing a structured format for tracking deliverables and managing task dependencies.

Do I need to define acceptance criteria before task decomposition for CI failure analysis?

Task decomposition handles CI failure analysis by breaking it into subtasks, but acceptance criteria are defined during the manifest generation phase. The process systematically maps deliverables and estimates effort to ensure clarity before dispatching roles.

Why use subtask decomposition instead of assigning a full feature request to a single Developer role?

Subtask decomposition breaks complex tasks into logical phases, enabling intelligent dispatching to appropriate AI roles and mapping dependencies. This approach identifies parallelizable work and critical paths that a single role assignment would miss.