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.

sarveshtalele Updated

File contents

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.

sarveshtalele/mcp-skills-registry/tree/main/skills/factory/task-decomposition commit 2ef50928fd

Frequently asked questions

npx skillmds@latest add sarveshtalele/task-decomposition