task-tree

Convert a goal into hierarchical Taskwarrior fork subtask trees from Markdown headings and bodies.

23|2|Updated Mar 1, 2026

Search Tags:#markdown #workflow execution #task planning #agent handoff #taskwarrior #subtask tree

Ready to run

npx skills add https://github.com/tta-lab/ttal-cli --skill task-tree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-tree
Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/task-tree
Command: npx skills add https://github.com/tta-lab/ttal-cli --skill task-tree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a goal into a concrete, reviewable execution plan by using taskwarrior fork subtask trees as the source of truth for what workers should do.

Core Features & Use Cases

Decomposition into steps: Convert a goal into a hierarchical subtask tree where each subtask is a single actionable step.
In-tree annotations: Store detailed instructions directly in the body text under headings so workers can read the plan without extra linking.
Safe iteration patterns: Support appending, full replacement, reordering, moving, and promoting subtasks to keep plans accurate across revisions.
Review and execution handoff: Provide workers with the plan structure via the parent task tree, enabling consistent workflow progression.

Quick Start

Create a new task plan by piping markdown headings into task <parent-uuid> plan so the resulting subtask tree becomes the executable workflow.

Frequently Asked Questions about task-tree

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

FAQPage Schema

How do I convert markdown headings into a taskwarrior subtask tree?▼

Markdown headings become an executable hierarchical plan when piped into the parent task plan command, using heading levels for nesting depth and body text for worker annotations.

What is the best way to turn a high-level goal into an executable taskwarrior plan?▼

Decomposing a goal into a hierarchical subtask tree provides a reviewable execution plan where each subtask represents a single actionable step, enabling consistent workflow progression and worker handoff across the pipeline.

Can I safely append revisions to an existing taskwarrior subtask tree without losing data?▼

Yes, taskwarrior fork subtask trees support safe iteration patterns including non-destructive appending, full replacement, reordering, moving, and promoting subtasks to keep plans accurate across revisions without losing worker annotations.

Does taskwarrior support storing detailed worker instructions directly in the task body?▼

Taskwarrior subtask trees store detailed instructions directly in the body text under headings as in-tree annotations, allowing workers to read the executable plan structure without needing extra external linking or documentation.

When should I use destructive replace versus non-destructive append for taskwarrior subtasks?▼

Use non-destructive append to add new steps or annotations to the subtask tree while preserving existing worker data, and use destructive replace only when completely overwriting a flawed plan structure that requires full revision.