菜单
Launch multiple Claude Code instances in parallel using tmux and git worktrees to tackle beads tasks concurrently. Use when user mentions parallel execution, multi-agent, parallel claude, or wants to run multiple Claude instances simultaneously on different tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full development workflow from idea to parallel execution. Use when planning features/bugfixes/refactors, breaking work into beads tasks, selecting tasks to parallelize (max 4), launching Claude instances in tmux worktrees, and cleaning up after completion. Triggers: "plan feature", "plan refactor", "plan bugfix", "start parallel work", "launch parallel", "cleanup worktrees", "kill parallel", or /dev-workflow.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Guide for adding new AI platform support (e.g., Gemini, Mistral, Anthropic) to the Chrome extension with strategy pattern and testing requirements
Ensure all UI components follow the design guidelines including purple-indigo gradient, rounded-xl borders, backdrop-blur-sm effects, dark mode support, and accessibility requirements
Automated detection and enforcement of design system guidelines including dark mode, colors, spacing, typography, focus states, and accessibility compliance
Automate version bumping, changelog generation, and release preparation. Creates release PR that triggers GitHub Actions workflow for building, testing, and publishing.
| name | parallel-claude |
| description | Launch multiple Claude Code instances in parallel using tmux and git worktrees to tackle beads tasks concurrently. Use when user mentions parallel execution, multi-agent, parallel claude, or wants to run multiple Claude instances simultaneously on different tasks. |
Launch N Claude instances in parallel using tmux + git worktrees to tackle beads tasks concurrently.
bd ready
Format output as table:
| ID | Pri | Type | Title |
|---|---|---|---|
| abc | P1 | bug | Fix memory leak |
| def | P2 | task | Add validation |
Evaluate tasks for parallelization:
Good candidates:
Bad candidates:
Hard limit: Max 4 tasks per group
CRITICAL: Present pre-analyzed groupings, not individual tasks.
{
"questions": [{
"question": "Which parallel grouping would you like to run?",
"header": "Parallel",
"multiSelect": false,
"options": [
{
"label": "Auth + UI bugs (Recommended)",
"description": "abc, def | Different modules, no overlap"
},
{
"label": "All 3 independent tasks",
"description": "abc, def, ghi | Touch separate dirs"
},
{
"label": "Single task: abc",
"description": "Safe if unsure about conflicts"
}
]
}]
}
Once user selects, launch directly (script claims issues automatically):
.claude/skills/parallel-claude/scripts/launch.sh abc def
tmux Navigation:
Ctrl+B, arrows - Switch panes
Ctrl+B, z - Zoom/unzoom pane
Ctrl+B, d - Detach (instances keep running)
Reattach:
tmux attach-session -t claude-parallel
# Check status
.claude/skills/parallel-claude/scripts/launch.sh --status
# Kill tmux only
.claude/skills/parallel-claude/scripts/launch.sh --kill
# Full cleanup (tmux + worktrees)
.claude/skills/parallel-claude/scripts/launch.sh --cleanup