do-in-parallel

Orchestrates parallel sub-agents to execute independent tasks across multiple files with judge verification.

1.5k|154|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill do-in-parallel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-in-parallel
Source: https://github.com/NeoLabHQ/context-engineering-kit/tree/main/plugins/sadd/skills/do-in-parallel
Command: npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill do-in-parallel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running the same or related tasks across many files sequentially is slow and error-prone, and unverified agent output often ships with defects. This Skill dispatches independent tasks to parallel sub-agents with per-task model selection and LLM-as-a-judge verification so batch work finishes faster and meets a quality bar.

Core Features & Use Cases

  • Parallel sub-agent orchestration: Dispatches implementation agents concurrently across files or named targets after validating task independence.
  • Requirement grouping: Identifies repeatable, shared, and independent task groups to reduce the number of meta-judge and judge agents without losing evaluation accuracy.
  • Per-task model selection: Assigns haiku, sonnet, or opus tiers per task based on scope, complexity, and risk, with escalation rules on retry.
  • LLM-as-a-judge verification: Meta-judges generate evaluation specs and judges score each result, with up to 3 retries per target.
  • Use Case: Apply the same error-handling refactor across a dozen source files at once, with each file's change independently verified against a generated rubric before being accepted.

Quick Start

Ask the agent to run do-in-parallel with a task description and a comma-separated --files or --targets list, optionally adding --model or --strict flags.

Frequently Asked Questions about do-in-parallel

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

FAQPage Schema
How do I run the same task across multiple files in parallel with AI agents?

Invoke do-in-parallel with a task description and a --files list of comma-separated paths. The orchestrator validates independence, dispatches one implementation sub-agent per file concurrently, and verifies each result with a judge agent.

How does per-task model selection work for parallel agents?

Each task is tiered independently as haiku, sonnet, or opus based on scope, complexity, and risk rules. Mechanical single-file edits default to haiku, standard code writing to sonnet, and critical or multi-file contract changes to opus, unless a --model override is passed.

When can tasks not be run in parallel?

Parallelization is unsafe when targets share files, modify shared state, depend on execution order, or read each other's output. If any independence check fails, the skill stops and recommends sequential execution instead.

What is LLM-as-a-judge verification in this workflow?

A meta-judge agent first generates an evaluation specification with rubrics and scoring criteria for the task. After implementation completes, a separate judge agent scores the result against that spec, and failures trigger retries with feedback up to 3 attempts.

What happens when a parallel task fails verification?

The judge's specific issues are fed back into a retry of only the failing task, up to 3 attempts. Low-quality first attempts escalate the model tier one step, while fixable defects may retry at the same tier.