dispatching-parallel-agents
/dispatching-parallel-agents
Use when multiple frozen subtasks have non-overlapping write sets and can be implemented or reviewed in parallel.
- Author
- funky-eyes ↗
- Repository
- best-copilot ↗
- Licence
- Apache-2.0
- Last repository change
- 04.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when multiple frozen subtasks have non-overlapping write sets and can be implemented or reviewed in parallel.
Original author description
Use when multiple frozen subtasks have non-overlapping write sets and can be implemented or reviewed in parallel.
How it works
- Preconditions
- Fan-out Packet
- Model, Permission, And Token Boundaries
- Fan-in
SKILL.md preview
--- name: dispatching-parallel-agents description: "Use when multiple frozen subtasks have non-overlapping write sets and can be implemented or reviewed in parallel." --- # Dispatching Parallel Agents ## Preconditions - Each subtask has goal, files, dependencies, material assumptions or explicit unknowns, acceptance checks, and verification. - Write sets do not overlap. - Shared foundation work is already done or assigned as a dependency. - Fan-in owner is identified. ## Fan-out Packet Each parallel subtask uses the six-block PM dispatch packet from `core-workflow-contract`. At minimum include: - `task_intent`: `goal`, `task_type`, `work_mode` - `frozen_scope`: `files_involved`, `write_set`, `dependencies`, `owner_lane`, `reviewer_lanes`, `review_package_ref`, `diff_ref` - `execution_contract`: `assumptions`, `tradeoffs`, `simpler_option_considered`, `constraints`, `acceptance_checks`, `verification_budget`, `model_policy`, `model_cost_boundary`, `cost_boundary`, `reviewer_input_boundary`, `reviewer_permission_boundary`, `forbidden_approaches`, `read_before_write_targets` when code edits are planned - `output_contract`: required skills, `required_artifacts` Add `sub_task_id` for fan-in tracking. ## Model, Permission, And Token Boundaries - Every parallel dispatch records the intended `owner_lane`, `reviewer_lane`, `permission_mode`, `write_set`, `review_package_ref` or `diff_ref`, `model_policy`, and `model_cost_boundary`. - When the runtime supports subagent model selection, choose the cheapest adequate explicit model/tier for each lane instead of inheriting the current session default. If model selection is not enforceable, state that in `model_policy` and `model_cost_boundary.enforcement`. - Batch fan-out that uses many reviewers, high-tier models, or repeated large context requires PM-visible cost acknowledgement or a cheaper explicit model/context strategy before dispatch. - Review-only lanes use read-only permission mode and must not run mutating git/workspace commands. Reclassify to fix/implementation before allowing edits. - Shared diffs, specs, logs, and review packages should be referenced once and reused by path or shard, not pasted into every subagent prompt. ## Fan-in Adjudicate fan-in using the priority order from `core-workflow-contract` Fan-In Arbitration. Accept only structured handbacks with the required fields. Merge results by dependency order. Re-run integration verification after combining parallel work.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · funky-eyes/best-copilot | 90 | Apache-2.0 |
| jjuraszek/pi-gauntlet | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| coco-research/coco | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| rootcastleco/rei-skills | 100 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| Richicinschi/studio-os | 100 | MIT |
Database snapshot: 13.11.2026 · package version 3e38f82922d6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100loom-dispatching-parallel-agents
Dispatch multiple independent tasks to parallel subagents when no shared file conflicts exist. Use when: a confirmed plan has independent tasks that can run concurrently without touching shared files. - 100sr-dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies - 100orchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion. - 100parallel-execution
Use when multiple subtasks have no shared files or dependencies and can be executed simultaneously.