parallel-dev

To run parallel Claude Code sessions, you can generate a CLI script that spawns multiple claude -p instances. This Skill creates a parallel-dev.sh script to orchestrate batch-based task execution for large features with many independent micro-tasks.

Orchestrating large-scale development across frontend and backend teams requires executing independent micro-tasks concurrently. This Skill generates a parallel CLI script that runs multiple Claude Code instances simultaneously, enabling faster iteration for cross-team collaboration.

Yes, you need a local claude CLI installed to run parallel development scripts. The generated parallel-dev.sh script relies on the claude -p command to spawn multiple external sessions, and it requires a current session plan in the .claude/sessions directory.

Parallel script generation handles session management by reading the current plan from .claude/sessions and writing results for each batch. The script orchestrates multiple claude -p sessions concurrently, managing 8 or more independent micro-tasks within a single feature workflow.

You should avoid using parallel CLI scripts for Claude Code automation when your feature lacks many independent micro-tasks. The approach is designed for large-scale batch execution of 8 or more concurrent sessions, making it unsuitable for tightly coupled or sequential development tasks.

Using parallel-dev for features with fewer than 8 independent micro-tasks is not recommended. The Skill is specifically built for large features requiring batch-based task execution, where spawning multiple parallel Claude Code instances provides meaningful iteration speed gains.