execute-batched-loop

Executes pending task queues using three parallel sub-agents with chunked atomic git commits.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill execute-batched-loop-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-batched-loop
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/execute-batched-loop
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill execute-batched-loop-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating large backlogs of pending development tasks manually leads to merge conflicts, lost progress on crashes, polluted git history, and inconsistent execution. This Skill orchestrates a disciplined multi-agent loop that processes task queues from .ai-memory/plans/pending/ with file-collision locking, crash recovery, and enforced commit hygiene. ## Core Features & Use Cases - Batched Multi-Agent Execution: Runs exactly 3 concurrent sub-agents, each assigned small disjoint micro-task chunks tracked in a locking matrix to prevent git merge conflicts. - Crash Recovery & State Tracking: Logs agent state to .ai-memory/temp/ and .ai-memory/temp-agents/, applies a 3-strike rollback policy with git checkout, and resumes from failure points. - Atomic Commits & CI/CD Discipline: Consolidates all changes into single atomic commits, bans local test/build execution (deferred to CI/CD), and monitors pipelines via GitMap Pipeline-AI with ETA-based waiting. - Use Case: A repository has 40 pending task files in .ai-memory/plans/pending/. Invoke this Skill to autonomously loop through all of them—spawning agents, committing chunks, consolidating completed plans—until the queue is empty. ## Quick Start Ask the agent to execute all pending tasks from the plans folder using the batched loop, and say "continue" to resume the loop until the queue is empty.

Frequently Asked Questions about execute-batched-loop

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

FAQPage Schema
How do I run a batch of pending tasks with multiple AI agents?

Place task files in .ai-memory/plans/pending/ and invoke this Skill. It spawns up to 3 concurrent sub-agents, assigns each a disjoint chunk of micro-tasks, and self-loops until the queue is empty, committing progress atomically.

How do I prevent parallel AI agents from causing git merge conflicts?

The Skill uses a file collision locking matrix registered in .ai-memory/01-index.md. Each agent is assigned tasks touching completely disjoint files, and all changes are accumulated into a single atomic commit rather than per-file commits.

What happens when a sub-agent crashes during task execution?

Agent state is logged to .ai-memory/temp/ before execution. On failure, the Skill inspects the state, and after 3 failures it reverts dirty changes with git checkout, logs the root cause, and restarts a new agent on the next chunk.

Does this workflow run tests or builds locally?

No. The Skill imposes a total ban on running tests (go test, pytest) and build checks (go build, npm run build) during routine execution. All verification is deferred to CI/CD, monitored via GitMap Pipeline-AI with ETA-based waiting.

When should I not use a batched multi-agent loop?

Avoid it for single small tasks, repositories without a structured pending-task queue, or work requiring local test-driven iteration. The overhead of locking, state tracking, and chunked commits only pays off on multi-task backlogs.