task-breakdown

Decompose features into sequenced tasks with dependencies and acceptance signals.

Updated May 9, 2026

Search Tags:#task breakdown #delegation #acceptance criteria #sprint planning #project execution #dependency mapping #workflow decomposition

Ready to run

npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill task-breakdown-gustavogutierrez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-breakdown
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/task-breakdown
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill task-breakdown-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid ambiguous, overly large work items by decomposing complex features, epics, or specs into small, verifiable tasks with clear sequencing, dependencies, and acceptance signals.

Core Features & Use Cases

Executable task decomposition: Break scope into independently deliverable units with concrete outcomes.
Sequencing, dependencies, and parallelization: Identify critical path work, prerequisite foundations, and tasks that can run concurrently.
Issue-tracker readiness: Produce a structured task list with completion criteria and verification methods suitable for delegation and planning.

Example: You have a multi-step feature that spans UI behavior, domain rules, data changes, and validation; use this skill to generate a wave-based plan of deliverables, dependency mappings, and test/verification steps for each task.

Quick Start

Use the task-breakdown skill to produce a task breakdown for the feature described below, including dependencies, parallelization notes, and acceptance criteria.

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 complex epics into executable tasks for sprint planning?▼

Task breakdown for project execution involves decomposing features into small, independently deliverable units sequenced in waves, mapping dependencies, and defining acceptance criteria to ensure each increment is verifiable before delegation.

What is the best way to map dependencies and parallelize workflow decomposition?▼

The best way to map dependencies during workflow decomposition is to identify critical path prerequisites and group concurrent tasks into execution waves, enabling parallelization while maintaining clear scope boundaries.

How do I create acceptance criteria for delegated agent tasks?▼

You create acceptance criteria for delegated tasks by defining concrete deliverable outcomes, explicit validation methods, and scope boundaries for each work unit, ensuring agents can independently verify incremental completion.

Can I use task decomposition for backlog grooming without embedding project-specific assumptions?▼

Task decomposition supports backlog grooming without project-specific assumptions by enforcing deliverable-outcome task sizing, explicit dependency mapping, and structured wave outputs that maintain scope boundaries for general execution.

When should I not use automated task breakdown for feature planning?▼

Avoid automated task breakdown when features lack defined deliverable outcomes or clear specifications, because the decomposition process requires concrete inputs to accurately map dependencies, sequencing, and validation methods.