Skill

parallel-power

Multi-session and parallel execution patterns. Worktrees, fan-out, writer/reviewer splits. Use when you need to work on multiple things simultaneously.

Install

npx claudepluginhub artmin96/forge-studio --plugin reference

Tool Access

This skill uses the workspace's default tool permissions.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Pattern 1: Parallel Worktrees

Work on multiple features simultaneously with zero conflicts:

claude --worktree feature-auth # Isolated copy, own branch claude --worktree bug-fix-123 # Another isolated copy claude --worktree # Auto-generated name

Each worktree gets its own branch from origin/HEAD. Changes are isolated. Cleanup is automatic if no changes were made.

Tip: Copy .env and other gitignored files by creating .worktreeinclude:

.env .env.local config/secrets.json

# Generate task list claude -p "list all controllers that need auth middleware" > tasks.txt # Process each while read file; do claude -p "add auth middleware to $file" --allowedTools "Read,Edit" done < tasks.txt

Parallel Power: Do More at Once

Pattern 1: Parallel Worktrees

Work on multiple features simultaneously with zero conflicts:

claude --worktree feature-auth     # Isolated copy, own branch
claude --worktree bug-fix-123      # Another isolated copy
claude --worktree                  # Auto-generated name

Each worktree gets its own branch from origin/HEAD. Changes are isolated. Cleanup is automatic if no changes were made.

Tip: Copy .env and other gitignored files by creating .worktreeinclude:

.env
.env.local
config/secrets.json

Pattern 2: Writer/Reviewer Split

Use SEPARATE sessions for writing and reviewing — fresh context prevents bias:

Session 1: Write the code
Session 2: claude --resume or new session → review the code
Fresh context means the reviewer isn't anchored to the implementation decisions

Pattern 3: Fan-Out Batch Processing

Process multiple files with the same operation:

# Generate task list
claude -p "list all controllers that need auth middleware" > tasks.txt

# Process each
while read file; do
  claude -p "add auth middleware to $file" --allowedTools "Read,Edit"
done < tasks.txt

Pattern 4: Orchestrator-Workers (Subagents)

For large features with independent subtasks:

Create a plan with independent work items
Ask Claude to dispatch subagents for each item
Each subagent works in isolation, returns a summary
Main session synthesizes results

Sweet spot: 3-5 parallel agents. More than that is hard to review.

Pattern 5: Session Per Concern

Don't mix unrelated tasks. Instead:

claude -n "auth-refactor" — session for auth work
claude -n "api-tests" — session for test writing
claude -n "bug-4521" — session for a specific bug
Resume any with claude --resume auth-refactor