impl-orchestration

Name: impl-orchestration
Availability: InStock
Author: aimeerrhythm

Coordinate parallel implementation tasks with dependency-aware layered workflows.

1|Updated Apr 12, 2026

Search Tags:#subagents #orchestration #worktree #parallel-execution #dependency-graph #code-merge #risk-review

Ready to run

npx skills add https://github.com/Aimeerrhythm/enterprise-change-workflow --skill impl-orchestration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impl-orchestration
Source: https://github.com/Aimeerrhythm/enterprise-change-workflow/tree/main/skills/impl-orchestration
Command: npx skills add https://github.com/Aimeerrhythm/enterprise-change-workflow --skill impl-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating implementation work across large projects is slow and error-prone when changes cascade across teams. This Skill orchestrates the end-to-end process by dispatching specialized subagents in dependency-aware parallel layers, followed by controlled merges and reviews to ensure quality, traceability, and faster delivery.

Core Features & Use Cases

Parallel dispatch of independent tasks to subagents with worktree isolation to maximize throughput.
Sequential merges with conflict handling, verification checks, and architectural traceability.
Parallel spec reviews and P0-focused code-quality checks to ensure correctness and maintainability.
Pre-flight checks, dependency-graph-driven layering, and automatic ledger updates for each layer.
Suitable for large-scale change management where multi-domain coordination and risk-aware gating are required.

Quick Start

Provide an implementation plan and let ecw orchestrate parallel subagents with layer-by-layer reviews.

Frequently Asked Questions about impl-orchestration

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

FAQPage Schema

How do I coordinate parallel implementation tasks across a dependency graph?▼

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.

What is the best way to run parallel code merges without breaking dependencies?▼

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.

How do automated spec reviews and code-quality checks work during parallel execution?▼

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.

Can I use parallel subagent orchestration for large-scale change management?▼

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.

Do I need an implementation plan before starting parallel subagent dispatch?▼

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.

Why does dependency-aware layering matter for parallel code execution?▼

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.