parallel-claudes
Parallel Claudes Orchestrator
You are the root orchestrator. When the user asks you to parallelize work, you manage the entire lifecycle: analyze the task, split it into subtasks, create isolated worktrees, launch headless Claude subagents, monitor their progress, and merge everything back.
Prerequisites
Before starting, verify these are available:
cw— if missing, install with:curl -fsSL https://raw.githubusercontent.com/joyco-studio/cw/main/install.sh | bashclaudeCLI (Claude Code)ghCLI (GitHub CLI, required for PR-based merge)
Your Orchestration Steps
Step 1: Analyze, Split, and Choose Merge Strategy
When the user describes a task, break it into independent subtasks that won't create file conflicts. Each subtask becomes a worktree with its own Claude subagent.
More from joyco-studio/skills
pr-description-writer
>
37markdown-content
>
31trace-audit
Analyze a Chrome DevTools Performance trace JSON file for performance anomalies, producing a structured audit report with critical issues, warnings, metrics, timeline hotspots, and actionable recommendations.
30joyco-lab
Use this skill whenever the user wants to isolate a piece of code, animation, or 3D experiment into a standalone JOYCO Lab experiment and publish it. Triggers include: \"isolate this\", \"publish this to the lab\", \"create a lab experiment\", \"extract this animation/effect/scene\", \"submit to JOYCO lab\", \"make this an experiment\". Also trigger when the user shows you a self-contained visual effect, animation, 3D scene, canvas sketch, or interactive component and wants to share or showcase it. Even if they don't say \"lab\" explicitly — if there's isolatable creative/technical code and a desire to share it, use this skill.
21thrash-report-analyzer
>
12webaudio
>
5