decompose-plan

Decompose plan documents into structured beads with epics and dependencies.

1|Updated Jan 9, 2026

Search Tags:#beads #epics #plan #task-management #decompose

Ready to run

npx skills add https://github.com/Dunc4nJ/entropy-plugins --skill decompose-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decompose-plan
Source: https://github.com/Dunc4nJ/entropy-plugins/tree/main/bead-pipeline/skills/decompose-plan
Command: npx skills add https://github.com/Dunc4nJ/entropy-plugins --skill decompose-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Complex feature specifications and implementation plans often sit as dense documents. This skill breaks those plans into structured, self-contained beads grouped into epics with clear dependencies and context, enabling autonomous multi-agent execution and traceable progress.

Core Features & Use Cases

Bead-based decomposition: Split a plan into beads representing discrete tasks, with epic groupings to reflect phases or milestones.
Dependency-aware scheduling: Establish parent-child relationships so work can be ordered and blockers identified.
Self-contained Beads: Each bead includes a complete description, acceptance criteria, context, and notes for future self.
Decomposition logging: Record decisions and the resulting bead graph for auditing and reproducibility.

Quick Start

Provide the path to your plan document to begin decomposing into beads.

Frequently Asked Questions about decompose-plan

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

FAQPage Schema

How do I decompose a software project plan into actionable tasks for multi-agent execution?▼

Decomposing a plan involves breaking dense specifications into structured, self-contained beads grouped into epics with clear dependencies and context, enabling autonomous multi-agent execution and traceable progress.

What are beads and epics in task management decomposition?▼

Beads represent discrete tasks derived from a plan, while epics are groupings that reflect phases or milestones. Beads include descriptions, acceptance criteria, context, and notes to ensure self-contained execution.

How do I establish task dependencies when breaking down a feature specification?▼

Dependency-aware scheduling establishes parent-child relationships between beads during decomposition. This allows work to be ordered correctly and identifies blockers across the task graph before execution begins.

Can I use a dense plan document directly for automated task scheduling?▼

Yes, you can provide the path to your plan document to begin decomposition. The process applies rigorous analysis to determine epic boundaries, bead scope, dependencies, and context distribution automatically.

How are decomposition decisions logged for auditing and reproducibility?▼

Decomposition logging records all decisions and the resulting bead graph during the breakdown process. This ensures the structured task output can be audited and reproduced for future reference or validation.