orchestrating-as-epic

Coordinate epic-level software delivery across multiple Claude Code sessions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill orchestrating-as-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrating-as-epic
Source: https://github.com/tuvens/phased-development/tree/main/skills/orchestrating-as-epic
Command: npx skills add https://github.com/tuvens/phased-development --skill orchestrating-as-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates long-running software epics so multiple Claude Code sessions can plan, dispatch, review, and merge work without losing branch discipline or cross-session awareness.

Core Features & Use Cases

  • Epic Orchestration: Manages epic-level planning, sprint creation, merge order, and final PR delivery.
  • Cross-Session Coordination: Uses signals, status-board updates, and wake protocols to keep leadership and sprint sessions synchronized.
  • Release Guardrails: Enforces testing, regression review, branch-base checks, shutdown requests, and merge authorization rules.
  • Use Case: A team running a multi-month GitHub project can use this Skill to launch sprints, track blockers, consolidate results, and ship an epic safely.

Quick Start

Use the orchestrating-as-epic skill to coordinate an epic branch, dispatch sprints, and produce the final PR workflow for a multi-phase Claude Code project.

Frequently Asked Questions about orchestrating-as-epic

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

FAQPage Schema
How do I coordinate sprint planning across multiple Claude Code sessions for a GitHub project?

Sprint planning across multiple Claude Code sessions is coordinated by orchestrating epic phases and dispatching sprints. This Skill uses worktrees and cross-session signals to synchronize leadership and sprint sessions while maintaining branch discipline.

What is the best way to manage epic branches and enforce merge sequencing in Claude Code?

Epic branch management and merge sequencing are enforced through strict branch-convention rules and guarded merge authorization. This Skill coordinates regression rollups and final pull request preparation to ensure safe epic delivery.

How do cross-session signals work when orchestrating long-running software epics?

Cross-session signals work by using status-board updates and wake protocols to keep leadership and sprint sessions synchronized. This ensures multiple Claude Code sessions maintain awareness of blockers and progress during long-running epics.

Can I use worktrees to dispatch sprints and track blockers in a multi-phase GitHub project?

Yes, you can use worktrees to dispatch sprints and track blockers in a multi-phase GitHub project. This Skill coordinates sprint dispatch, tracks blockers via status boards, and consolidates results for final pull request delivery.

Does epic orchestration require testing and review checkpoints before merging GitHub branches?

Epic orchestration requires testing, regression review, and branch-base checks before merging GitHub branches. Release guardrails enforce shutdown requests and guarded merge authorization to ensure safe consolidation of sprint results.

When should I avoid using automated sprint dispatch for Claude Code projects?

You should avoid automated sprint dispatch for Claude Code projects lacking strict branch conventions or testing checkpoints. This Skill requires enforced branch discipline, regression rollups, and merge authorization rules to safely coordinate epic delivery.