manager-loop

Coordinate parallel worker agents across git worktrees with heartbeat-driven dispatch and merge gating.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/patrickserrano/lacquer --skill manager-loop-patrickserrano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manager-loop
Source: https://github.com/patrickserrano/lacquer/tree/main/core/skills/manager-loop
Command: npx skills add https://github.com/patrickserrano/lacquer --skill manager-loop-patrickserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a large batch of independent work items one at a time wastes time and stalls progress between messages. This Skill turns multi-unit batches — fleet-wide harvests, multi-repo syncs, overnight backlogs — into a persistent coordinator loop that dispatches workers, monitors progress on a heartbeat, routes feedback, and gates merges without waiting on a human trigger between steps. ## Core Features & Use Cases - Parallel worker dispatch: Spins up one background agent per unit of work, each on its own git worktree, branch, and PR, with an explicit directive to keep going until the branch is actually mergeable. - Heartbeat scheduling: Uses scheduled wakeups to re-check in-flight PRs, CI status, and stuck workers at an interval matched to the batch's pace instead of idling between notifications. - Feedback routing and merge gating: Resumes the same worker with review feedback rather than re-implementing fixes, and requires green builds, tests, and lint plus a manual diff read before merging. - Use Case: You need to apply the same migration across 15 repositories. Dispatch one worker per repo, let the heartbeat loop track each PR's CI status, route review comments back to the responsible worker, and merge each branch only after checks pass and you have read the diff. ## Quick Start Ask the AI to run this batch of independent tasks as a manager loop with one worker per repository and a heartbeat to track PR status until all are merged.

Frequently Asked Questions about manager-loop

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

FAQPage Schema
How do I run the same task across many repositories in parallel?▼

Dispatch one background worker agent per repository, each on its own git worktree and branch with its own PR. A coordinator loop then tracks progress on a heartbeat, routes feedback back to each worker, and merges only after checks pass.

What is the difference between manager-loop and subagent-driven-development?▼

Manager-loop fits batches of genuinely independent units, each getting its own worktree, branch, and PR. Subagent-driven-development fits a single feature with sequential subtasks on one branch, using a fresh subagent per subtask with review between each.

When should I not use a coordinator loop for batch work?▼

Avoid it for a single task with one thread of work, since there is nothing to coordinate. Also avoid it when units are so interdependent that they must run in order with full context carried forward between steps.

How does the coordinator handle a PR that fails review or CI?▼

The coordinator resumes the same worker via message with the specific feedback instead of fixing it in a fresh agent or in the coordinator's own thread. The worker retains its worktree and history, which re-dispatching would lose.

Does a green build mean a worker's PR is safe to merge?▼

No. Green builds, tests, and lint are required but not sufficient. The coordinator must still read the diff before merging, since passing checks do not prove the approach was right or that nothing was overreached.