Skill for creating parallel development plans with multiple developers. Leverages git worktree for branch strategy, task dependency analysis, critical path calculation, developer role assignment, and timeline creation. Use for requests like "create a parallel development plan", "I want to develop with multiple people simultaneously", "divide work with worktree", or "maximize development parallelization". Also supports on-demand parallel tasks for quick fixes with requests like "fix XX in parallel", "do YY with worktree", or "add parallel task".
/plugin marketplace add hiroshi75/ccplugins/plugin install parallel-dev-plugin@hiroshi75This skill inherits all available tools. When active, it can use any tool Claude has access to.
references/advanced-features.mdreferences/quick-mode-guide.mdreferences/scripts/cleanup-worktrees.shreferences/scripts/setup-quick-task.shreferences/scripts/status.shreferences/scripts/update-dashboard.shreferences/scripts/watch-signals.shreferences/templates/merge-coordinator.mdreferences/templates/parallel-dev-readme.mdreferences/templates/task-instruction.mdreferences/testing-guide.mdreferences/ui-approval-guide.mdreferences/worktree-guide.mdscripts/cleanup-parallel-dev.shscripts/create-done-file.shscripts/create-issue-file.shscripts/setup-worktree.shscripts/start-coordinator.shscripts/start-worker.shscripts/stop-worker.shCreate implementation plans to maximize parallelization of feature development with multiple developers. Also supports on-demand parallel tasks (bug fixes, feature additions) for completed projects.
This skill has two modes:
Used immediately after project initialization (right after uv init, create-react-app, etc.) when developing multiple features in parallel.
Trigger Phrases:
Workflow: 9-step workflow (described below) to create a plan and start multiple tasks simultaneously.
Used for bug fixes and feature additions to projects with existing implementations. Start work immediately without a plan document.
Trigger Phrases:
Workflow: See "Quick Task Workflow" section for details.
| Situation | Recommended Mode |
|---|---|
| Right after project initialization, parallel features | A |
| Single bug fix to existing project | B (single task) |
| Medium-scale feature addition to existing project | B (multiple tasks + merge coordinator) |
1. Understand Requirements
└─→ Collect list of features to develop
└─→ Confirm tech stack (BE/FE/Infrastructure, etc.)
2. Task Decomposition
└─→ Split each feature into independent tasks
└─→ Granularity: whichever is smaller
├─→ 0.5-2 days in human time
├─→ Within 20 files changed
└─→ Independently testable feature unit
└─→ ⚠️ UI specs require human approval (see below)
3. Dependency Analysis
└─→ Identify blocking relationships between tasks
└─→ Calculate critical path
4. Determine Parallelism
└─→ Calculate number of Claude instances needed
└─→ Assignment to minimize wait time
5. Branch Strategy
└─→ Design integration branch
└─→ Feature branch naming convention
└─→ Determine merge order
6. Create Timeline
└─→ Gantt-style parallel schedule
7. Create Plan and Instruction Documents
└─→ Communicate plan content to user (present execution order, parallelism, and task content in table format)
└─→ Create files in .parallel-dev/
├─→ PLAN.md (plan document)
├─→ README.md (overall overview and progress management)
├─→ merge-coordinator.md (for merge coordinator)
├─→ tasks/*.md (for each task)
├─→ signals/ (completion notification directory)
└─→ issues/ (issue report directory)
8. Environment Setup
└─→ Create integration branch and push to remote
└─→ Create worktree for each task
└─→ Install dependencies in each worktree
└─→ Copy .env in each worktree
9. Launch merge coordinator Claude in tmux new-window
└─→ Create new window with tmux new-window -n "coordinator" and launch claude
└─→ Pass initial instructions to merge coordinator
Mode for immediately starting bug fixes or feature additions to existing projects without a plan document.
Features:
.parallel-dev/quick-session-{timestamp}.md)→ See references/quick-mode-guide.md for details
To avoid confusion, unify the following terms:
| Term | Description | Example |
|---|---|---|
| Task Name | Identical to branch name. Work unit ID | skill-files-api, recommendation-ui |
| Person/Role | Worker identifier. Tech area + number | BE-1, FE-1, INFRA-1 |
| Integration Branch | Target branch to merge all tasks | feature/multi-file-skills |
Important: Use task name (branch name) for completion reports and state management. Person name alone cannot identify the task when handling multiple tasks.
Task splitting principles:
Branch naming:
feature/recommendation-api # Feature name based
feature/notification-api
feature/project-card-enhance
Role (person) naming:
BE-1, BE-2, ... # Backend
FE-1, FE-2, ... # Frontend
INFRA-1, ... # Infrastructure
Dependency types:
| Dependency Type | Symbol | Description |
|---|---|---|
| Blocking | → | Must complete |
| Parallel | // | Can proceed independently |
| Waiting for integration | ↓ | Start after merge |
Critical path calculation:
Longest path = max(total effort of each path)
Optimal number of people = ceil(total effort / critical path)
Create dependency matrix:
BE-01 BE-02 FE-01 FE-02
BE-01 - // ↓ //
BE-02 // - // ↓
FE-01 Wait // - //
FE-02 // Wait // -
Role definition template:
| Role | Assigned Branch | Required Skills |
|---|---|---|
| BE-1 | feature/xxx-api | Python, FastAPI |
| FE-1 | feature/xxx-ui | React, TypeScript |
Principles for minimizing wait time:
Git worktree basics for parallel development:
main
└── feature/integration (integration branch)
├── feature/xxx-api → worktree/xxx-api/
├── feature/yyy-api → worktree/yyy-api/
└── feature/xxx-ui → worktree/xxx-ui/
→ See references/worktree-guide.md for details
For parallel development with Claude, place instruction documents for each Claude in .parallel-dev/.
Directory Structure:
| Directory/File | Purpose |
|---|---|
.parallel-dev/ | Parallel dev management (git-managed) |
.parallel-dev/PLAN.md | Plan document |
.parallel-dev/merge-coordinator.md | For merge coordinator |
.parallel-dev/tasks/*.md | Instruction docs per task |
.parallel-dev-signals/ | Completion notifications (.gitignore) |
.parallel-dev-issues/ | Issue reports (.gitignore) |
Templates:
Role Division:
.done file (don't commit)Design Philosophy: Worker Claude focuses on writing code. Only merge coordinator manages merge order.
→ See references/worktree-guide.md for details
tmux new-window -n "{task-name}" (don't use Task tool)tmux new-window -n "{task-name}" "cd worktree/{task-name} && PROJECT_ROOT=$PROJECT_ROOT claude 'Please read ../../.parallel-dev/tasks/{task-name}.md and implement. Create \$PROJECT_ROOT/.parallel-dev-signals/{task-name}.done when complete (create in parent project, not in worktree).'"
tmux send-keys -t "{task-name}" C-c C-c--no-ff→ See references/worktree-guide.md for details
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.