execute-all-tasks

Batch-run repository tasks with dependency-aware ordering and isolated git worktrees.

41|4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/etr/groundwork --skill execute-all-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-all-tasks
Source: https://github.com/etr/groundwork/tree/main/skills/execute-all-tasks
Command: npx skills add https://github.com/etr/groundwork --skill execute-all-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates batch execution of all remaining tasks in a repository, ensuring clean baselines, dependency-aware ordering, and safe integration via isolated work trees and staged task phases.

Core Features & Use Cases

  • Dependency-aware topological scheduling of tasks based on a formal tasks file or specs directory
  • Per-task isolation using git worktrees with automatic merge after successful completion
  • End-to-end batch lifecycle (plan, implement, validate, and merge) with status tracking and failure handling

Quick Start

Invoke this skill to start batch execution of all remaining tasks in dependency order with isolated work trees.

Frequently Asked Questions about execute-all-tasks

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

FAQPage Schema
How do I automate batch task execution with dependency order in a git repository?

Batch task execution automates running remaining repository tasks in dependency order using isolated git worktrees, automatic per-task planning, validation, and safe merge procedures.

What is the best way to manage multi-task workflows with isolated git worktrees?

Managing multi-task workflows with isolated git worktrees involves dependency-aware topological scheduling, per-task isolation, and end-to-end lifecycle tracking from planning through merge.

How does task orchestration handle validation and merge procedures for TDD workflows?

Task orchestration enforces a TDD-first development cycle by applying per-task validation with a suite of quality reviewers before executing safe merge procedures into the main branch.

Do I need a specific tasks file format to run batch task orchestration?

Yes, batch task orchestration requires multi-task workflows defined in a tasks.md file or a tasks directory, with task statuses tracked as Not Started, In Progress, Complete, or Blocked.

What happens to isolated worktrees when a batch task fails during validation?

When a batch task fails during validation, the system preserves the isolated worktrees for investigation rather than discarding them, allowing developers to debug the failure safely.