task-decomposer

Break down complex tasks into interdependent subtasks with verification criteria.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Alteriom/ai-dev-skills --skill task-decomposer-alteriom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-decomposer
Source: https://github.com/Alteriom/ai-dev-skills/tree/main/skills/task-decomposer
Command: npx skills add https://github.com/Alteriom/ai-dev-skills --skill task-decomposer-alteriom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down complex tasks into manageable subtasks with clear dependencies and verification criteria, enabling predictable delivery and better planning.

Core Features & Use Cases

  • Dependency mapping and critical path identification for project planning.
  • Vertical slicing to deliver end-to-end functionality in small increments.
  • Establishing task-level verification criteria to ensure clear definitions of done.

Quick Start

Break down a feature into steps with dependencies and measurable success criteria.

Frequently Asked Questions about task-decomposer

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

FAQPage Schema
How do I break down complex tasks into subtasks with dependencies?

To break down complex tasks into interdependent subtasks, you map dependencies, apply vertical slicing for end-to-end increments, and establish clear verification criteria for predictable delivery.

What is vertical slicing in agile planning?

Vertical slicing in agile planning is a decomposition technique that breaks features into small, end-to-end functional increments, enabling iterative delivery and clear dependency mapping across subtasks.

How can I establish task-level verification criteria for project planning?

You establish task-level verification criteria by defining measurable success metrics and definitions of done during task decomposition, ensuring each subtask has clear risk framing and delivery guardrails.

Can I use task decomposition for dependency mapping and critical path identification?

Yes, task decomposition applies to dependency mapping and critical path identification, helping software teams enforce interdependent subtask tracking and iterative delivery scoping for agile features.

What's the best way to scope software delivery for iterative increments?

The best way to scope software delivery is applying vertical slicing to decompose complex tasks into interdependent subtasks, framing risks and enforcing measurable success criteria for each increment.

When should I not use vertical slicing for feature decomposition?

Vertical slicing for feature decomposition may not suit projects lacking clear end-to-end functionality or when critical path dependencies are too rigid to allow small, iterative delivery increments.