By ken2403
Parallel Workflow - Generic parallel development workflow for large-scale tasks. Includes Agent Teams integration for enhanced parallel execution.
Launch an agent team to collaboratively discuss, critique, and validate a specification before decomposing it into parallel-executable tasks.
Parse review feedback and spawn agent team for parallel fixes
Implement a task using an agent team in the current directory. No worktree creation, no automatic commits — the lead asks before shipping.
Create an isolated git worktree, then create an agent team to implement the task in parallel. Run autonomously through PR creation without requiring user approval.
Identify conflicting files and resolve in parallel via agent team
Deep codebase analysis for understanding architecture, patterns, and complex dependencies. Use when thorough understanding is needed before major changes.
Fast codebase exploration for finding files, patterns, and code locations. Use for quick searches before implementation. Optimized for speed over thoroughness.
Lightweight implementation agent for small to medium code changes (under ~200 lines). Assesses task scope before implementation and rejects tasks that are too complex. Use for quick fixes, small features, and minor refactors.
Background status monitoring agent. Checks worker progress every 30 seconds and reports completion or errors. Designed to run in background while orchestrator continues other work.
Code quality standards for reviewing code changes. Activated when reviewing PRs, implementing features, or discussing code quality. Triggers on requests to "review code", "check quality", "improve code", or "refactor".
Reviews PR changes against the broader codebase to find inconsistencies, missed propagation, and stale references beyond the diff. Replicates senior reviewer codebase knowledge. Activates when reviewing PRs, checking consistency, or when changes touch shared entities across multiple files.
Security review checklist for code changes. Automatically activates when reviewing security-sensitive code, authentication, authorization, or data handling. Use when user asks to "check security", "review for vulnerabilities", "audit code", or when changes touch auth, crypto, user input, or API endpoints.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Runs pre-commands
Runs pre-commands
Contains inline bash commands via ! syntax
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
A Claude Code plugin for parallel development environments using Git worktree and tmux.
Maximizes development efficiency by decomposing large development tasks into multiple independent subtasks and executing them in parallel.
Clone from GitHub. The plugin can be placed in any directory:
# Clone to any directory
cd /path/to/any-directory
git clone https://github.com/ken2403/claude-paralell-dev-plugin.git
Example layout:
/opt/claude-plugins/
└── claude-paralell-dev-plugin/ # This plugin
Add PW_PLUGIN_DIR to your shell profile so that plugin scripts (e.g. base branch detection) are always discoverable:
# Add to ~/.zshrc (or ~/.bashrc)
echo 'export PW_PLUGIN_DIR="/path/to/any-directory/claude-paralell-dev-plugin"' >> ~/.zshrc
source ~/.zshrc
Registering the plugin as a Marketplace makes it available in any project:
# Add the plugin as a Marketplace
claude plugin marketplace add /path/to/any-directory/claude-paralell-dev-plugin
# Install the plugin
claude plugin install pw@claude-parallel-dev-plugin
To use only in a specific session, launch Claude Code with the --plugin-dir option:
cd your-project
claude --plugin-dir /path/to/any-directory/claude-paralell-dev-plugin
cp ../claude-paralell-dev-plugin/examples/CLAUDE.project-template.md ./CLAUDE.md
# Edit to fit your project
This plugin supports three workflows:
Receive spec → Design (with decomposition) → Parallel execution → Review → Merge → Cleanup
Use this when decomposing into multiple subtasks and executing in parallel with tmux.
Issue/Task → wt-j → (Autonomous implementation) → Review → Merge → Cleanup
Use this when autonomously implementing independent tasks in an isolated environment.
Issue/Task → at-design → at-j → at-rv → at-fix → at-resolve-conflicts → merge → wt-clean
Or for quick in-place implementation without worktree:
Task → at-impl → (review changes) → commit
Uses Claude Code's experimental Agent Teams feature for multi-agent parallel execution. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
| Command | Description | Arguments |
|---|---|---|
/pw:design | Create design and decompose tasks from spec | #issue-number / @file-reference / "text" |
/pw:orchestrate | Launch parallel workers | List of branch names |
/pw:worker | Execute worker task | Task description |
/pw:wt-j | Autonomous implementation in isolated worktree (parallel for 3+ files) | #issue-number / "task description" [--feature|--fix] |
/pw:wt-clean | Clean up wt-j environment | job-name / --all |
/pw:status | Check progress | (Optional) session name |
/pw:precheck | Pre-check before PR creation | Branch name or HEAD |
/pw:rv | Review PR (critical) | PR number |
/pw:fix | Fix review feedback (parallel for 3+ files) | Feedback content |
/pw:merge | Merge PR | PR number [--skip] |
/pw:cleanup | Clean up environment | List of branch names |
/pw:resolve-conflicts | Resolve conflicts (parallel for 3+ files) | Branch name |
/pw:at-design | Agent team spec discussion and task decomposition | #issue-number / @file-reference / "text" |
/pw:at-j | Agent team implementation in isolated worktree | #issue-number / "task description" [--feature|--fix] |
/pw:at-rv | Agent team parallel PR review (3 specialists) | PR number |
/pw:at-fix | Agent team parallel review feedback fixes | PR number |
/pw:at-impl | Agent team implementation in current directory | #issue-number / @design-document / "task description" |
/pw:at-resolve-conflicts | Agent team parallel conflict resolution | Branch name |
# Design (includes task decomposition)
/pw:design #123
# Launch parallel workers
/pw:orchestrate feature/auth feature/api feature/tests
# Check progress
/pw:status
# PR review
/pw:rv 45
# Merge
/pw:merge 45
npx claudepluginhub ken2403/claude-paralell-dev-plugin --plugin hvManage large coding tasks using git worktrees and background Claude Code sessions. Supports launching, monitoring, resuming, and cleanup of autonomous tasks with alert notifications.
Parallel task orchestration for AI coding agents - dispatch work to Codex or Claude Code workers in isolated git workspaces
Subagents and hooks for TTAL multi-agent orchestration
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts
Unified spec-to-execution workflow system. Combines spec rigor, autonomous execution, and native task orchestration with parallel agent dispatch. Swarms-ready architecture.
Autonomous GitHub Project Management workflow with orchestrator-agent coordination for parallel task execution via git worktrees