# Task Decomposition

> Convert a specification into a structured, dependency-ordered backlog as tasks.yaml with stories, tasks, estimates, and acceptance checks. Trigger on: decompose tasks, create backlog, convert spec to tasks, planning, work items.

- Skill: `sarveshtalele/task-decomposition` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add sarveshtalele/task-decomposition`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sarveshtalele/task-decomposition/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: sarveshtalele (https://skillmd.com/u/sarveshtalele)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/sarveshtalele/task-decomposition

---


# task-decomposition

Convert a specification summary into a dependency-ordered backlog (`tasks.yaml`)
with stories, tasks, estimates, and acceptance checks.

## When to use
After a spec/plan is approved. Triggers: *decompose tasks, create backlog,
convert spec to tasks, work items*.

## Inputs
- `spec_summary` (string, required).
- `num_stories` (integer, optional, default 3, clamped 1–12).

## Outputs
- `tasks_yaml` — YAML backlog.
- `story_count`, `task_count`.

## How it works
For each story it scaffolds design → implement → test tasks with linear
dependencies and acceptance placeholders, emitting valid YAML.

## User stories
- *As a delivery lead*, I turn a spec into a structured backlog ready for Jira
  import (see `jira_templates/`).

## Edge cases
- `num_stories` out of range → clamped.
- Quotes in the summary → escaped so the YAML stays valid.

## Files
See [DOCS.md](DOCS.md).