skills.rest
edercnj
edercnjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

x-orchestrate-epic

Orchestrates multi-agent epic planning by invoking per-story planners in dependency order.

Updated Aug 27, 2026
Search Tags:#multi-agent#epic planning#orchestrate#dependency-order#execution-state.json#planning-status
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-orchestrate-epic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-orchestrate-epic
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-orchestrate-epic
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-orchestrate-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates multi-agent planning for all stories in an epic by invoking per-story planners in dependency order, updating a central execution-state.json to enable checkpointing and resume.

Core Features & Use Cases

  • Phase-based planning across epic stories with parallel dispatch within phases
  • Tracks per-story planning status (PENDING, IN_PROGRESS, READY, NOT_READY) and DoR verdicts
  • Generates planning artifacts, reports, and updates the epic file as planning progresses
  • Supports dry-run and resume flows to ensure durable planning state

Quick Start

Run /x-orchestrate-epic <EPIC-ID> to start planning all stories in the epic with checkpoint and resume support.

Frequently Asked Questions about x-orchestrate-epic

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

FAQPage Schema
How do I orchestrate epic planning across multiple agents with dependency ordering?▼

Multi-agent epic planning is orchestrated by invoking per-story planners in dependency order, dispatching parallel agents within phases, and tracking progress via a central execution-state.json file for checkpointing and resume support.

What is the best way to track per-story planning status and DoR verdicts in a multi-agent workflow?▼

Per-story planning status and DoR verdicts are tracked through a central execution-state.json file, which records states like PENDING, IN_PROGRESS, READY, and NOT_READY to enable durable checkpointing and accurate resume flows.

Can I resume multi-agent epic planning if the execution stops midway?▼

Yes, multi-agent epic planning supports resume flows by reading the durable execution-state.json file, allowing the orchestration to restart from the last committed wave checkpoint without losing prior planning artifacts.

Does multi-agent epic orchestration support dry-run flows for planning validation?▼

Yes, the orchestration supports dry-run flows to validate the multi-agent planning process, ensuring phase-based dependency ordering and per-story readiness checks execute correctly before generating final artifacts and reports.

When do I need phase-based planning with parallel dispatch for epic stories?▼

Phase-based planning with parallel dispatch is needed for epics containing multiple stories with dependencies, where independent stories within the same phase can be planned concurrently by separate agents to optimize execution time.

Related Skills

Explore More Software Engineering Skills→
robotics-playgroundrobotics-playground

bmad-sprint-planning

Parse epic files to generate a complete sprint-status.yaml.

Official
Intermediate
bahayonghangbahayonghang
16

omo-agents

Coordinate seven specialized AI agents for collaborative development tasks.

Community
Basic
ArvorCoArvorCo
96

prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

Community
Basic
woxiangyangzhimaowoxiangyangzhimao
3

batch

Execute sequential code changes with checkpoints and rollback.

Community
Advanced