dispatching-parallel-agents

Dispatches independent tasks to parallel subagents with tiered model routing and batching.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/dariovr1/sixth-sense --skill dispatching-parallel-agents-dariovr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/dariovr1/sixth-sense/tree/main/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/dariovr1/sixth-sense --skill dispatching-parallel-agents-dariovr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running multiple independent coding tasks sequentially wastes time, while dispatching subagents without a plan causes file conflicts, wrong model choices, and wasted budget. This Skill provides a structured protocol for decomposing work, routing each task to the right model tier, and coordinating parallel subagents safely. ## Core Features & Use Cases - Effort Routing: Assigns each task to a model tier (haiku-batch, sonnet-low/medium/high, opus-high, smart-search) based on file count, complexity, and architectural impact. - Batching and Agent Caps: Groups same-shape tasks into single dispatches and limits concurrent agents (default 4) to control cost and conflicts. - Dispatch Ledger and Fix Loop: Logs every dispatch per campaign in .sixth-sense/dispatch-log/<slug>.md, resumes interrupted campaigns, and runs a capped 5-round escalation loop for failed tasks. - Use Case: When implementing a feature spanning 8 independent files, present a dispatch plan table, get user confirmation, then run 4 parallel subagents at appropriate tiers while logging progress for resumability. ## Quick Start Break this feature into independent tasks and dispatch parallel subagents with the right model tier for each one.

Frequently Asked Questions about dispatching-parallel-agents

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

FAQPage Schema
How do I run multiple AI coding tasks in parallel?

Decompose the work into independent tasks with no shared files, present a dispatch plan assigning each task a model tier, get user confirmation, then launch subagents. Cap concurrent agents at 4 by default and log each dispatch in a per-campaign ledger.

How do I choose which model tier to use for a coding subtask?

Route by scope: single-file changes under 20 lines go to haiku-batch, 1-3 file tasks to sonnet-low, business logic across 2-5 files to sonnet-medium, and architectural decisions to sonnet-high. Reserve opus-high for novel design work or final escalation.

When should tasks not be dispatched to parallel agents?

Skip parallel dispatch when tasks share state, modify the same files, or depend on each other's output. Sequential or tightly coupled work should be executed iteratively instead, since concurrent agents editing the same file cause conflicts.

What happens when a parallel subagent's work fails verification?

Failed tasks enter a capped fix loop: rounds 1-3 re-dispatch the same tier with the findings, round 4 escalates one tier with fresh context, and round 5 escalates to opus-high. After round 5, remaining findings are adjudicated directly and logged.

Can subagents invoke skills or follow skill instructions by name?

No. Subagents have Read access but cannot invoke skills by trigger phrase. Inline the concrete rules directly in the dispatch prompt, or give the exact file path to a reference file for the subagent to read itself.