task-decomposition

Decompose complex tasks into atomic subtasks with dependency graphs and DAG specifications.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill task-decomposition-baekenough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-decomposition
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/task-decomposition
Command: npx skills add https://github.com/baekenough/second-brain --skill task-decomposition-baekenough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down large, complex tasks into atomic subtasks that can be executed in parallel within a DAG-based workflow, enabling scalable planning and execution.

Core Features & Use Cases

  • Atomic subtask generation with single-responsibility scope
  • Dependency mapping and DAG specification for orchestration
  • Parallel execution planning across multiple agents or domains
  • Use Case: plan a multi-team feature rollout by decomposing requirements into independently testable units with clear dependencies.

Quick Start

Provide a DAG-ready decomposition plan for a given task by breaking it into atomic subtasks and identifying dependencies.

Frequently Asked Questions about task-decomposition

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

FAQPage Schema
How do I decompose a complex project into parallel subtasks for DAG orchestration?

To decompose tasks for DAG orchestration, you break complex requirements into atomic subtasks with single-responsibility scope, map their explicit dependencies, and generate a DAG specification for parallel execution planning.

What is a DAG-ready task decomposition plan for multi-team projects?

A DAG-ready task decomposition plan splits large-scale cross-domain tasks into independently testable atomic units, maps their dependency graph, and outputs a workflow specification suitable for multi-agent parallel execution.

Can I use this task decomposition approach for cross-domain planning across multiple teams?

Yes, task decomposition applies to large-scale planning across multi-team projects and cross-domain tasks by generating atomic subtasks with clear boundaries and explicit dependencies for parallel orchestration.

What's the best way to map dependencies when breaking down complex tasks into subplans?

The best way to map dependencies is by defining clear subtask boundaries and explicit dependencies within the generated DAG specification, ensuring atomic subtasks are structured for parallel execution.

Do I need explicit subtask boundaries to generate a workflow specification for orchestration?

Yes, generating a workflow specification for DAG orchestration requires clear subtask boundaries and explicit dependencies to correctly sequence atomic subtasks for parallel execution planning.

Why does parallel execution planning require atomic subtasks with single-responsibility scope?

Parallel execution planning requires atomic subtasks with single-responsibility scope to ensure clear subtask boundaries and explicit dependencies, enabling scalable DAG-based workflow orchestration without execution conflicts.