task-decomposition

Transform user requests into directed acyclic graphs of agent-assignable tasks.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill task-decomposition-pact-community-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-decomposition
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/task-decomposition
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill task-decomposition-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform user requests into a directed acyclic graph of agent-assignable tasks to orchestrate multi-agent workflows.

Core Features & Use Cases

  • Classifies requests into feature, bug, security, docs, or support.
  • Builds a task graph with fields like id, type, title, assignee, dependencies, gate, priority, acceptance_criteria, status.
  • Validates DAGs to prevent cycles and ensure clear owners, prerequisites, and proper gating.

Quick Start

Provide a user request and have the system decompose it into a task graph with initial assignees.

Frequently Asked Questions about task-decomposition

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

FAQPage Schema
How do I turn user requests into an executable task graph for multi-agent coordination?

To turn user requests into an executable task graph, the system classifies the request and builds a directed acyclic graph (DAG) of agent-assignable tasks with fields like assignee, dependencies, and acceptance criteria.

How does DAG validation prevent workflow cycles in project management?

DAG validation prevents workflow cycles by checking the task graph for circular dependencies, ensuring clear owners, validating prerequisites, and enforcing proper gate-based workflows before task delegation.

Can I classify support and bug tickets into a structured workflow automatically?

Yes, you can classify support and bug tickets automatically, as the system categorizes user requests into feature, bug, security, docs, or support workflows before creating the task graph.

What is the best way to decompose a feature request into tasks with clear dependencies?

The best way to decompose a feature request is to map it into a task graph structure, specifying task types, assignees, priorities, and dependencies to orchestrate the work across specialist agents.

Do I need to define acceptance criteria before generating a task graph?

No, you do not need to define acceptance criteria beforehand, as the graph generation process automatically structures user requests into tasks complete with acceptance criteria and status tracking.

What happens if my project management workflow has missing prerequisites or gating?

If prerequisites or gating are missing, DAG validation will fail to ensure clear owners and proper prerequisites, preventing the system from delegating work across specialists until the graph is corrected.