run-tasks

Orchestrate end-to-end tasks using beads and labeled sub-agents.

2|3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/dot-do/dotdo --skill run-tasks-dot-do
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tasks
Source: https://github.com/dot-do/dotdo/tree/main/.claude/skills/run-tasks
Command: npx skills add https://github.com/dot-do/dotdo --skill run-tasks-dot-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end task execution by pulling ready work from beads, spawning appropriate agents based on labels, tracking progress, and updating bead state to drive complex project workflows.

Core Features & Use Cases

  • Orchestrates multi-agent batches with optional TDD gating and telemetry collection after each agent.
  • Supports parallel work with git worktrees and per-task docs for traceability.
  • Updates beads status and propagates results to downstream steps, enabling iterative epic progression.

Quick Start

Use this command: Start the run-tasks workflow for a given epic after /approve-spec has created tasks.

Frequently Asked Questions about run-tasks

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

FAQPage Schema
How do I orchestrate multi-agent task execution for ready work items?

Multi-agent task orchestration pulls ready work from beads and spawns agents by label, tracking progress and updating bead state to drive complex project workflows. It supports parallel batching with git worktrees and telemetry capture.

How does task gating work with TDD in an agent orchestration workflow?

TDD gating in task orchestration requires tests to pass before work proceeds. Agents pull labeled work, execute tasks, and only update bead status to success when TDD requirements are met, ensuring quality control across parallel batches.

Can I run parallel agent batches using git worktrees for isolated task execution?

Yes, parallel agent batches run using git worktrees to isolate task execution. Each agent works in a separate worktree, captures telemetry after completion, and stores results in a per-epic docs path while squashing commits on success.

What labels do I need to spawn sub-agents for task management?

Spawning sub-agents requires labels like agent:<type> to match agents to tasks, and optional skip_tests labels to bypass TDD gating. These labels drive how ready work is pulled from beads and assigned to appropriate agents.

How do beads and sub-agents coordinate end-to-end epic progression?

Beads and sub-agents coordinate epic progression by pulling ready work, spawning labeled agents, capturing telemetry, and propagating results to downstream steps. Status updates flow back to beads, enabling iterative and traceable epic advancement.

What's the best way to track task results and commits in a multi-agent workflow?

The best way to track task results is storing outputs in a per-epic docs path and squashing commits on success. Telemetry is captured after each agent completes, and bead statuses are updated to propagate results to downstream workflow steps.