batch-task-execution

Plans and executes batches of tasks from todo lists using parallel sub-agents.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill batch-task-execution-siegenthalerroger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-task-execution
Source: https://github.com/siegenthalerroger/.llmctl-marketplace/tree/main/plugins/llmctl-core-0.4.0/skills/batch-task-execution
Command: npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill batch-task-execution-siegenthalerroger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working through a backlog or multi-item request with sub-agents often leads to unconfirmed scope, overlapping file edits, lost context, and unreviewed results. This Skill provides a disciplined protocol for confirming, grouping, dispatching, and reviewing batches of tasks so nothing is silently skipped or broken. ## Core Features & Use Cases - Confirmation Gate: Presents the proposed task selection, grouping, and assumptions to the user before any agent is launched or file is changed. - Parallelisation and Sizing Rules: Groups independent tasks, assigns one sub-agent per group, and tiers work between Executor (Focused) for tasks touching up to 5 files and Executor (Broad) for cross-component work. - Dispatch Briefs and Outcome Protocol: Defines a cold-start dispatch format with verbatim values and a four-status outcome model (DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, BLOCKED) with explicit handling for each. - Review Discipline: Enforces spec-compliance-then-quality review per task, a five-round fix cap with written rulings, and a final cross-batch review. - Use Case: Given a 12-item TODO list spanning several modules, confirm the plan with the user, fan out independent groups to sub-agents, review each diff, and keep the tracking file updated so progress survives context compaction. ## Quick Start Work through my TODO list as a batch: confirm the plan with me first, then run independent tasks in parallel sub-agents and review each result before moving on.

Frequently Asked Questions about batch-task-execution

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

FAQPage Schema
How do I run multiple tasks in parallel with sub-agents?▼

Group tasks by independence so no two agents share files, dependencies, or scope, then assign one sub-agent per group. Confirm the grouping with the user before launching, and state it explicitly so overlap can be spotted before agents start.

How should I size tasks for sub-agents?▼

Tier by how many files a task touches, counting both files read for context and files edited. Use a focused executor for tasks touching up to 5 files within one component, and a broad executor for 6 or more files or cross-component reasoning.

What should a sub-agent dispatch prompt include?▼

Include one line of batch context, exact values verbatim stated once, interfaces and decisions from earlier tasks, rulings on resolved ambiguities, and where the result must be reported. Never reference earlier conversation, since the agent starts cold.

Can conversational agents run as single-shot subagents?▼

Only when all design decisions are already resolved and the task is purely mechanical, such as writing up agreed requirements. If the agent's value is interactive dialogue, present the task to the user and recommend invoking that agent directly.

What happens when a sub-agent returns BLOCKED or NEEDS_CONTEXT?▼

For NEEDS_CONTEXT, supply the missing information and re-dispatch. For BLOCKED, classify the cause as missing context, wrong worker tier, oversized scope, or a defective task, then fix that cause rather than retrying an unchanged prompt.

How many fix rounds are allowed when reviewing sub-agent work?▼

Fix rounds are capped at five per task: rounds 1-3 go back to the same executor, rounds 4-5 go to a fresh broad executor. At the cap, every open finding gets a written ruling as overruled, deferred, or batch-stopping.