decomposer

Decompose high-level project phases into atomic Markdown step files.

Updated Jun 10, 2026

Search Tags:#automation #workflow #planning #multi-agent #project-management #task-decomposition

Ready to run

npx skills add https://github.com/jambolo/claude-skills --skill decomposer-jambolo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decomposer
Source: https://github.com/jambolo/claude-skills/tree/main/project-management/decomposer
Command: npx skills add https://github.com/jambolo/claude-skills --skill decomposer-jambolo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing large, complex project goals by breaking them down into small, manageable, and parallelizable steps that can be executed by subagents.

Core Features & Use Cases

Atomic Task Generation: Converts a high-level project phase into individual, self-contained step files.
Parallelization Logic: Ensures tasks are disjoint and parallelizable, preventing merge conflicts and coordination overhead.
Use Case: When you have a massive feature implementation phase, use this skill to generate specific, actionable step files for each sub-task, ensuring each worker has exactly the context it needs to succeed.

Quick Start

Use the decomposer skill to break the current project phase into atomic steps for the worker agents.

Frequently Asked Questions about decomposer

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

FAQPage Schema

How do I break down complex project phases into parallel tasks for multi-agent execution?▼

To break down complex project phases into parallel tasks, you need a decomposition mechanism that converts high-level phases into atomic, self-contained Markdown step files. This ensures subagents receive isolated context and disjoint tasks to prevent merge conflicts.

What is task decomposition in a multi-agent workflow pipeline?▼

Task decomposition in a multi-agent workflow pipeline is the process of projecting necessary context, defining acceptance criteria, and managing dependencies to split large project phases into parallelizable Markdown step files for independent subagent execution.

Do I need existing planner artifacts to use a task decomposition skill?▼

Yes, existing planner artifacts are required to use a task decomposition skill. These artifacts ensure consistent project state and scope isolation before generating atomic, parallelizable step files for worker agents.

How do I prevent merge conflicts when automating task distribution to subagents?▼

To prevent merge conflicts when automating task distribution, you must ensure generated tasks are disjoint and parallelizable. Decomposing phases into atomic step files provides each subagent with exactly the isolated context needed without coordination overhead.

What's the best way to define acceptance criteria for atomic project tasks?▼

The best way to define acceptance criteria for atomic project tasks is by using a decomposition process that projects necessary context and manages task dependencies within a multi-agent pipeline, ensuring each step file is self-contained.