impl-orchestration

Coordinate parallel implementation tasks by dispatching subagents across dependency-aware layers. This workflow isolates work via per-task worktrees, enforces risk-based review gates, and executes sequential merges to ensure code quality and alignment with the plan.

Run parallel code merges safely by isolating independent tasks in separate worktrees, then processing sequential merges with conflict handling. Dependency-graph-driven layering and staged verification checks ensure changes cascade without breaking the project.

Automated spec reviews and code-quality checks work by running parallel reviews focused on P0 risks after subagents execute. This ensures correctness and maintainability before changes pass through risk-aware gating and merge into the main branch.

Yes, you can use parallel subagent orchestration for large-scale change management. It adapts to project type through configurable models, enforces multi-domain coordination, and updates an automatic ledger for each dependency-aware layer.

Yes, you need an implementation plan before starting parallel subagent dispatch. The orchestration analyzes your plan dependencies to layer tasks, executes pre-flight checks, and dispatches specialized subagents to maximize throughput safely.

Dependency-aware layering matters for parallel code execution because it prevents cascading errors across teams. By isolating work in worktrees and enforcing risk-based review gates before sequential merges, it maintains architectural traceability and code quality.