backlog-execute

Executes backlog task files in parallel git worktrees with implementer-reviewer subagent pipelines.

1|Updated Dec 18, 2009
One-click install
npx skills add https://github.com/thurn/dotfiles --skill backlog-execute-thurn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-execute
Source: https://github.com/thurn/dotfiles/tree/main/.llms/skills/backlog-execute
Command: npx skills add https://github.com/thurn/dotfiles --skill backlog-execute-thurn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a queue of independent coding tasks one at a time is slow, and running them in parallel without structure leaves a pile of unmerged branches and manual cherry-pick cleanup. This Skill drains task files from /tmp/backlog/ by running multiple tasks concurrently in isolated git worktrees, each with an implementer and reviewer subagent, then serially integrates approved branches onto one linear integration branch. ## Core Features & Use Cases - Parallel task execution: Maintains a configurable number of concurrent feature slots (default 3), launching the next pending task the moment any slot frees. - Implementer-reviewer pipeline: Each task gets a fresh implementer subagent, a read-only reviewer subagent, and up to 3 review-fix rounds before being approved or failed. - Serial integration lane: A dedicated integrator subagent cherry-picks approved branches onto a single linear backlog/integration branch, with an escalation path to a repair subagent when mechanical cherry-picks fail. - Use Case: After generating 15 independent task files in /tmp/backlog/, invoke this Skill to grind through all of them in parallel and receive one clean integration branch ready to merge to master, plus a summary of integrated, failed, and blocked tasks. ## Quick Start Run backlog-execute to drain all task files in /tmp/backlog/ with parallel implementer and reviewer subagents and integrate the approved branches onto backlog/integration.

Frequently Asked Questions about backlog-execute

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

FAQPage Schema
How do I run multiple coding tasks in parallel with git worktrees?▼

Place independent task files in /tmp/backlog/ and invoke backlog-execute. It creates a separate git worktree and branch per task, dispatches implementer and reviewer subagents in the background, and maintains a target parallelism of 3 concurrent tasks by default.

How do I merge approved task branches without manual cherry-picking?▼

The skill runs a serial integration lane that cherry-picks each approved branch onto a single linear backlog/integration branch. If a mechanical cherry-pick fails, a repair subagent attempts scoped conflict resolution, so approved work does not pile up as unmerged branches.

Can backlog-execute handle tasks that depend on each other?▼

No. Parallel execution requires tasks to be independent against the same base commit, since each task branches from the same starting point. For ordered dependencies, use backlog-execute-serial or merge the dependent tasks into one task file first.

What happens when a task fails review or integration?▼

Tasks failing after 3 review rounds are recorded as failed; their worktree is removed but the branch is kept for inspection, and the task file stays in /tmp/backlog/. Integration failures escalate to a repair subagent, and a blocked repair stops further integration with an explicit report.

Does this skill work with both Claude Code and Codex?▼

Yes. The skill is harness-agnostic and documents mappings for both: Claude Code uses background Agent dispatch with automatic completion notifications, while Codex uses spawn_agent and wait_agent. Both share the same implementer, reviewer, and integrator prompt contracts.