Skill
account-research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM.…
@charlieviettqView SkillDevelopment
Skill
/dispatching-parallel-agents
Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.
Install
$ npx -y skills add charlieviettq/awesome-agent-skill --skill dispatching-parallel-agents --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dispatching-parallel-agents
Context preview
The summary Claude sees to decide when to auto-load this skill.
Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.
SKILL.md
dispatching-parallel-agents.SKILL.mdname: dispatching-parallel-agents
description: "Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files."
allowed-tools: Read, Glob, Grep
Dispatching parallel agents
Gate (required)
Use this skill **only if**:
- User or parent explicitly allows parallel subagents, **and**
- Tasks are independent (no shared files, no ordering dependency on partial output)
If either condition fails, use sequential `incremental-implementation` instead.
When to use
- Independent reviews (security + tests + API contract) on the same commit
- Parallel research spikes with separate output files
- Large plan with disjoint file ownership per task
When not to use
- Single shared module being edited by multiple agents
- Database migrations or sequential deploy steps
- User did not approve multi-agent execution
Workflow
1. **Partition** — list tasks with disjoint `Files:` sets 2. **Brief** — each agent gets scope, constraints, verify command, output format 3. **Dispatch** — run parallel agents; cap concurrency to what the harness supports 4. **Collect** — gather outputs without assuming correctness 5. **Integrate** — parent reconciles conflicts, runs full verification, single commit strategy per user rules
Integration checklist
- [ ] No conflicting edits to the same paths
- [ ] Combined diff reviewed by parent (or `requesting-code-review`)
- [ ] Full test/lint suite on integrated result
- [ ] User informed of what each agent did
Anti-patterns
- Parallel implementers on the same feature branch without file boundaries
- Merging subagent output without reading diffs
- Spawning agents to avoid reading the codebase
Related
`subagent-driven-development`, `incremental-implementation`, `requesting-code-review`, `verify-before-done`
*Orchestration patterns inspired by [obra/superpowers](https://github.com/obra/superpowers) (MIT).*
Read more
name: dispatching-parallel-agents description: "Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files." allowed-tools: Read, Glob, Grep
Dispatching parallel agents
Gate (required)
Use this skill **only if**:
- User or parent explicitly allows parallel subagents, **and**
- Tasks are independent (no shared files, no ordering dependency on partial output)
If either condition fails, use sequential `incremental-implementation` instead.
When to use
- Independent reviews (security + tests + API contract) on the same commit
- Parallel research spikes with separate output files
- Large plan with disjoint file ownership per task
When not to use
- Single shared module being edited by multiple agents
- Database migrations or sequential deploy steps
- User did not approve multi-agent execution
Workflow
1. **Partition** — list tasks with disjoint `Files:` sets 2. **Brief** — each agent gets scope, constraints, verify command, output format 3. **Dispatch** — run parallel agents; cap concurrency to what the harness supports 4. **Collect** — gather outputs without assuming correctness 5. **Integrate** — parent reconciles conflicts, runs full verification, single commit strategy per user rules
Integration checklist
- [ ] No conflicting edits to the same paths
- [ ] Combined diff reviewed by parent (or `requesting-code-review`)
- [ ] Full test/lint suite on integrated result
- [ ] User informed of what each agent did
Anti-patterns
- Parallel implementers on the same feature branch without file boundaries
- Merging subagent output without reading diffs
- Spawning agents to avoid reading the codebase
Related
`subagent-driven-development`, `incremental-implementation`, `requesting-code-review`, `verify-before-done`
*Orchestration patterns inspired by [obra/superpowers](https://github.com/obra/superpowers) (MIT).*
Ships withawesome-agent-skill
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
Get the whole plugin
Other skills on awesome-agent-skill.
@charlieviettqView SkillSkill
agent-evaluation
Evaluate LLM agents and tool-using workflows—task success, tool accuracy, latency/cost, safety, and regression suites. Use when shipping agent features,…
@charlieviettqView SkillSkill
agent-tool-contracts
Design agent tools and CLI surfaces—schemas, naming, errors, idempotency, and discoverability for LLM callers. Use when defining tools for agents, SDKs, or…
@charlieviettqView SkillSkill
algo-ad-bidding
\"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding…
@charlieviettqView SkillSkill
algo-ad-budget
\"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across…
@charlieviettqView SkillSkill
algo-ad-ctr
\"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad…
@charlieviettqView Skill