skills.rest
zb-ss
zb-ssOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Epic Orchestration Instructions

Orchestrate multi-component software workflows with isolated git worktrees and dependency-ordered merging.

1|1|Updated Feb 1, 2026
Search Tags:#git worktrees#multi-agent orchestration#dependency ordering#epic workflow#automated integration testing#rate limit resilience
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill epic-orchestration-instructions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Epic Orchestration Instructions
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/phases/epic-orchestration
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill epic-orchestration-instructions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of coordinating large, multi-component development efforts—planning architecture, implementing isolated components, merging changes safely, and running integration reviews and tests without losing state or getting stuck on rate limits.

Core Features & Use Cases

  • Epic architecture planning: Decomposes a project into non-overlapping components with explicit interfaces and a DAG dependency order.
  • Worktree-isolated component execution: Creates per-component git worktrees on dedicated branches, then runs executor/supervisor agents to implement and test within each isolated scope.
  • Dependency-wave orchestration: Executes components in parallel waves based on complexity and API quota, including rate-limit pause/resume behavior.
  • Integration and multi-pass validation: Merges components in topological order, resolves conflicts, runs full test suites, and enforces post-merge multi-architect zero-tolerance review.

Quick Start

Tell Claude to start the epic workflow for your project using the command: /workflow:start epic.

Frequently Asked Questions about Epic Orchestration Instructions

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

FAQPage Schema
How do I orchestrate multi-component software projects in parallel using git worktrees?▼

Multi-component software projects can be orchestrated by planning architecture, executing components in isolated git worktrees on dedicated branches, and merging them in dependency order. This enables parallelized implementation with automated PR creation per component.

What is the best way to manage dependency ordering when merging parallel feature branches?▼

Dependency ordering during merges is managed by decomposing a project into non-overlapping components with a DAG dependency order. Components are then merged in topological order to resolve conflicts and run full test suites systematically.

How do I handle API rate limits during automated multi-agent orchestration?▼

API rate limits during multi-agent orchestration are handled using shared rate-limit detection with automatic pause and resume behavior. The workflow adjusts dynamic parallelism decisions based on complexity and API quota availability.

Can I run automated integration testing across components in isolated git worktrees?▼

Automated integration testing across components is supported by running executor and supervisor agents within each isolated git worktree. After merging in topological order, full test suites and multi-architect zero-tolerance reviews validate the integrated pipeline.

Does epic workflow orchestration support stateful progress tracking for long-running tasks?▼

Epic workflow orchestration supports stateful progress tracking to maintain execution state across long-running tasks. This ensures the end-to-end pipeline does not lose state during parallelized implementation, conflict resolution, or rate-limit pauses.

What are the limitations of using automated dependency-wave orchestration for project merges?▼

Automated dependency-wave orchestration requires components to have explicit interfaces and non-overlapping scopes. It is not suitable for projects where components cannot be cleanly decomposed into a DAG dependency order or lack clear architectural boundaries.

Related Skills

Explore More Software Engineering Skills→
cenmiaocenmiao

openspec-sp-git-worktree

Create isolated Git worktrees with branch naming and baseline tests.

Community
Intermediate
huachenghuacheng
1

merge

Merge completed task branches into main with automated conflict resolution and verification.

Community
Advanced
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
curiositechcuriositech
10

dag-task-scheduler

Generates wave-based execution plans for DAG tasks with resource constraints.

Official
Advanced