bean-decomposition

Decompose development plan tasks into beans using TDD cycle estimates.

3|Updated Mar 12, 2026

Search Tags:#task decomposition #development planning #agile development #feature breakdown #bean sizing #tdd cycles

Ready to run

npx skills add https://github.com/peel/fiddle --skill bean-decomposition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bean-decomposition
Source: https://github.com/peel/fiddle/tree/main/skills/bean-decomposition
Command: npx skills add https://github.com/peel/fiddle --skill bean-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams accurately size tasks by determining whether a single task should be a standalone bean or a feature with multiple child tasks, based on estimated development effort.

Core Features & Use Cases

Task Sizing: Evaluates plan tasks to determine optimal bean structure (task vs. feature).
TDD Cycle Estimation: Uses a rule of thumb (3+ TDD cycles = feature) to guide decomposition.
Bean Generation Commands: Provides precise beans create commands for generating feature and task beans.
Dependency Management: Guides on setting up --blocked-by relationships between beans.
Use Case: When planning a new feature, this skill ensures that complex tasks are broken down into manageable sub-tasks, improving parallelization and tracking.

Quick Start

Use the bean-decomposition skill to determine the structure for a plan task that requires approximately 5 TDD cycles.

Frequently Asked Questions about bean-decomposition

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

FAQPage Schema

How do I break down development tasks into manageable sub-tasks?▼

Task decomposition breaks development plan tasks into appropriate bean structures based on estimated TDD cycles. If a task requires 3 or more TDD cycles, it is sized as a feature with multiple child tasks to ensure efficient implementation and tracking.

When should a development task be a standalone bean versus a feature?▼

A development task should be a standalone bean when it requires fewer than 3 TDD cycles. If the estimated TDD cycle budget reaches 3 or more, the task should be sized as a feature with multiple child tasks to improve parallelization.

How do I estimate TDD cycles for agile feature breakdown?▼

You estimate TDD cycles for agile feature breakdown by applying a rule of thumb budget per bean. This guides the decomposition process, determining whether a plan task generates a standalone bean or a feature with child tasks.

Can I set up dependencies between generated task beans?▼

Yes, dependency management guides setting up `--blocked-by` relationships between beans. This is part of generating precise `beans create` commands for feature and task beans within agile software development workflows.

Does bean sizing work without a predefined TDD cycle budget?▼

No, bean sizing requires adherence to a predefined TDD cycle budget per bean. This budget is necessary to evaluate plan tasks and determine the optimal bean structure for efficient implementation.

What is the best way to size tasks for parallel development tracking?▼

The best way to size tasks for parallel tracking is evaluating whether complex tasks require 3+ TDD cycles. This ensures they are broken down into manageable sub-tasks and features, generating precise bean creation commands with proper dependencies.