run-tasks

Orchestrate cross-agent task execution with TDD gating and telemetry collection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The run-tasks skill orchestrates cross-agent task execution within Claude Code projects by batching ready tasks, spawning specialized agents, and collecting telemetry to ensure reliable progress and completion.

Core Features & Use Cases

  • Batch and orchestrate tasks: Group ready tasks into sub-batches and run them in parallel where possible, with isolation via git worktrees.
  • TDD gating and verification: Support test-first development by gating implementation tasks behind tests, RED/GREEN/DEBUG loops, and verification steps.
  • Telemetry-driven retrospectives: Capture per-agent telemetry immediately after completion to feed /retro and improve future epics.

Quick Start

Invoke the run-tasks skill to begin orchestrating an epic workflow in Claude Code. For example: /run-tasks <epic-id> to start processing ready 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 cross-agent task execution in parallel batches?

Cross-agent task orchestration batches ready tasks into sub-batches and runs them in parallel using git worktrees for isolation, spawning specialized agents to process tasks concurrently while collecting telemetry for retro analyses.

How does TDD gating work for automated task verification?

TDD gating enforces test-first development by gating implementation tasks behind tests, running RED/GREEN/DEBUG cycles to verify code, and using stop-hook enforcement to ensure task completion before proceeding.

Can I use git worktrees to isolate parallel tasks across multiple agents?

Yes, git worktrees provide isolation for parallel batch execution, allowing agent-specific workers to operate independently on ready tasks without conflicts during cross-agent task orchestration.

What is the best way to collect telemetry for retrospective analysis after task completion?

Telemetry-driven retrospectives capture per-agent telemetry immediately after task completion, logging progress data that feeds retro analyses to improve future epic workflows and task batching strategies.

How do beads metadata drive automated task execution and progress logging?

Beads metadata provides the task structure that run-tasks reads to drive automated execution, verification, and progress logging, determining which tasks are ready for batching and agent-specific worker spawning.

What are the limitations of stop-hook enforcement in task orchestration?

Stop-hook enforcement ensures task completion within the orchestration cycle, but it requires tasks to be properly gated by TDD verification and beads metadata to function effectively across parallel agent batches.