task-breakdown

Decompose approved execution plans into task files with TASK-NNN IDs.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/buenhyden/hy-home.k8s --skill task-breakdown-buenhyden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-breakdown
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/task-breakdown
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill task-breakdown-buenhyden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose an execution plan into smaller, independently executable task units with clear acceptance criteria and evidence requirements, enabling precise tracking and verification by agents or operators.

Core Features & Use Cases

  • Transform approved plans (docs/04.execution/plans/) into task files (docs/04.execution/tasks/) with IDs (TASK-NNN).
  • Ensure each task includes goal, acceptance criteria, evidence, rollback, and a link to the parent plan.
  • Update the parent plan and governance memory with the created task references to maintain traceability.

Quick Start

Provide an approved plan file and let the system generate corresponding task units and templates for execution.

Frequently Asked Questions about task-breakdown

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

FAQPage Schema
How do I decompose an execution plan into agent-ready tasks with acceptance criteria?

Task breakdown transforms an approved execution plan into independently executable units, assigning each a TASK-NNN ID, acceptance criteria, and evidence requirements for precise tracking.

What is the best way to ensure one-to-one mapping between plan work items and generated task files?

Task decomposition enforces one-to-one mapping by generating task files under docs/04.execution/tasks using TASK-NNN IDs, directly referencing the parent plan items to maintain traceability.

How do I structure task files to include goal, rollback, and evidence tracking for governance?

Task files are structured using docs/99.templates/task.template.md as the base, ensuring each includes goal, acceptance criteria, evidence, rollback, and a link to the parent plan.

Does generating task units from a plan automatically update the parent plan and governance memory?

Yes, the task decomposition workflow updates the parent plan and governance memory with the created task references to maintain strict traceability and evidence tracking across the project.

Can I use this task decomposition workflow for plans stored outside the docs/04.execution/plans directory?

No, the task decomposition workflow specifically applies to approved plans under docs/04.execution/plans and produces task files under docs/04.execution/tasks to maintain the governance structure.