decompose

Decompose XL tasks into 3-7 sub-tasks with a dependency graph.

Updated Jun 1, 2025

Search Tags:#automation #project-management #sprint-planning #decompose #dependency-graph #task-planning #xl-task

Ready to run

npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill decompose-yokhan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/Yokhan/yokhanFitnessDocsWebsite/tree/main/.claude/skills/decompose
Command: npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill decompose-yokhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XL tasks often overwhelm teams during planning. Decompose them into smaller, manageable sub-tasks with clear dependencies to enable controlled execution.

Core Features & Use Cases

Automatically detect XL scope (tasks with >15 files or architecture changes) and generate 3-7 M-sized sub-tasks.
Create a Decomposition Plan detailing sub-task names, involved files, estimates, tests, and recommended commits, saved to tasks/current.md.
Pause execution after presenting the plan to allow user approval before proceeding.

Quick Start

Provide the XL task details and I will generate a decomposition plan and await your approval before execution.

Frequently Asked Questions about decompose

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

FAQPage Schema

How do I break down XL tasks into manageable sub-tasks for sprint planning?▼

To break down XL tasks, you can generate a decomposition plan that splits tasks exceeding 15 files or involving architecture changes into 3-7 sub-tasks with a dependency graph, file lists, and estimates.

When do I need to decompose a task before implementation?▼

You need to decompose a task when it reaches XL scope, specifically when it involves more than 15 files or requires architecture changes, enabling structured planning and controlled execution before implementation begins.

How does dependency graph generation work for large project tasks?▼

Dependency graph generation for large tasks maps relationships between 3-7 sub-tasks, detailing involved files, estimates, tests, and recommended commits, then saves the plan to tasks/current.md for user review.

Can I review and approve the decomposition plan before execution starts?▼

Yes, you can review and approve the decomposition plan before execution. The process pauses after generating sub-task details, file lists, and estimates, writing them to tasks/current.md to await your explicit approval.

What is the best way to manage task planning for architecture changes?▼

The best way to manage task planning for architecture changes is decomposing the XL scope into 3-7 M-sized sub-tasks with clear dependencies, estimates, and tests, ensuring controlled execution through a structured decomposition plan.

What limitations exist when decomposing tasks with a dependency graph?▼

A limitation of decomposing tasks is that it targets XL tasks specifically, generating between 3-7 sub-tasks, and requires user approval of the written plan before any implementation execution can proceed.