dev-parallel

Coordinate parallel implementation tasks across subagents with gated progress.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-parallel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-parallel
Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-parallel
Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-parallel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a single issue breaks into multiple independent implementation streams, dev-parallel keeps each subagent aligned with the plan, enforces consistent reviews, and prevents spec drift while ensuring gated progress.

Core Features & Use Cases

  • Independent Task Grouping: Analyzes implementation steps to detect sequences that can run concurrently and groups them for parallel execution.
  • Parallel Dispatch with Guardrails: Generates precise prompts, enforces mandatory builds and lint checks, and gates execution with a human-approved dispatch checkpoint.
  • Two-Stage Review Pipeline: Collects outcomes, runs spec compliance and code quality reviews via smart subagents, and loops on fixes before handoff.
  • Use Case: For a medium-sized feature branch touching shared modules, use dev-parallel to split the work into multiple subagents, reconcile results, and update the implementation document before shipping.

Quick Start

Run dev-parallel on your active feature branch to dispatch independent subagents, oversee the reviews, and finish the issue workflow.

Frequently Asked Questions about dev-parallel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate parallel implementation tasks across multiple subagents?

Parallel implementation tasks are coordinated by dispatching independent subagents to execute concurrently while enforcing prompt construction, mandatory build and lint runs, and gated progress checkpoints to prevent spec drift. Outcomes are collected and reviewed through a two-stage pipeline.

What is the best way to split a feature branch into independent task groups for concurrent development?

Splitting a feature branch involves analyzing implementation steps to detect sequences that can run concurrently, grouping them for parallel execution, and dispatching subagents with precise prompts to keep independent work aligned with specifications before reconciling results.

How do subagent code reviews handle spec compliance and code quality?

Subagent code reviews handle spec compliance and code quality through a two-stage review pipeline that collects outcomes, runs compliance and quality checks via smart subagents, and loops on fixes before final handoff to ensure alignment with the original plan.

Can I use parallel development for complex issue branches touching shared modules?

Parallel development suits complex issue branches touching shared modules by splitting work into multiple subagents, enforcing mandatory builds and lint checks, reconciling results, and updating implementation documentation before shipping.

When should I use automated subagent dispatch instead of sequential development?

Automated subagent dispatch is used when a single issue breaks into multiple independent implementation streams, requiring parallel execution with guardrails, human-approved dispatch checkpoints, and automated spec compliance reviews to prevent drift.

Does dev-parallel enforce mandatory builds and lint runs for each dispatched subagent group?

Dev-parallel enforces mandatory build and lint runs for each dispatched subagent group by applying gated progress checkpoints, constructing precise prompts, and requiring implementation documentation updates to maintain spec compliance.