breakdown-skill

Break approved plans into atomic tasks with dependencies and acceptance criteria.

7|Updated Feb 19, 2026

Search Tags:#planning #dependencies #acceptance criteria #estimation #task decomposition #execution readiness

Ready to run

npx skills add https://github.com/MajesteitBart/delano --skill breakdown-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: breakdown-skill
Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/breakdown-skill
Command: npx skills add https://github.com/MajesteitBart/delano --skill breakdown-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill breaks a completed plan into execution-ready tasks so a team or agent can move from planning to implementation without ambiguity.

Core Features & Use Cases

Atomic task decomposition: Converts a finished plan into small, actionable work items.
Dependency mapping: Orders tasks so prerequisites are explicit and circular dependencies are caught early.
Acceptance criteria and estimates: Adds binary completion checks plus effort signals for each task.
Use case: A delivery lead can hand this a validated plan and get a task set that is ready to assign, sequence, and execute.

Quick Start

Ask the agent to decompose the approved plan at the given path into atomic tasks with dependencies, acceptance criteria, and estimates.

Frequently Asked Questions about breakdown-skill

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

FAQPage Schema

How do I break an approved project plan into atomic execution tasks?▼

Task decomposition converts a completed plan into atomic execution tasks with explicit dependencies. It breaks the specification into actionable work items with binary acceptance criteria to remove ambiguity before implementation begins.

How do I map task dependencies and prevent circular dependencies in delivery planning?▼

Dependency mapping orders execution tasks so prerequisites are explicit and circular dependencies are caught early. It builds an acyclic dependency graph to support safe execution preparation and correct implementation sequencing.

What are binary acceptance criteria and why do I need them for task decomposition?▼

Binary acceptance criteria are strict pass or fail completion checks applied to each decomposed task. They are required to ensure every atomic task has a definitive completion condition before execution sequencing begins.

Can I use task decomposition for an existing validated plan without rewriting it?▼

Task decomposition applies directly to delivery planning workflows where a completed specification already exists. You provide the approved plan path and it generates execution-ready task files without altering the original validated plan.

Does task decomposition require per-task estimates for execution readiness?▼

Per-task estimates are required to achieve execution readiness. The decomposition process adds effort signals alongside binary acceptance criteria and acyclic dependency graphs to ensure safe implementation sequencing.