Split independent work items and run them in parallel through subagents. Use when a request names several areas that do not share files.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add korchasa/flowai --skill orchestrate-work --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Orchestrate Work?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/korchasa-orchestrate-work)More formats (shields.io, HTML) on the badges page.
---
name: orchestrate-work
description: Split independent work items and run them in parallel through subagents. Use when a request names several areas that do not share files.
---
# Orchestrate Work
## Rules
<rules>
1. Split the request into work items and check whether they share files. Items
that share a file are NOT independent and must run in sequence.
2. Fan independent items out to subagents, one item per worker.
3. Merge the workers' results before reporting.
4. If parallel execution is unavailable in the current environment, proceed
sequentially and say so.
</rules>
## Step-by-step
<step_by_step>
1. Enumerate the work items named in the request.
2. For each pair, decide whether they touch the same files.
3. Dispatch every independent item to its own worker.
4. Collect the workers' output and merge it.
5. Report what each worker produced.
</step_by_step>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...