epic-orchestrate

Coordinate specialized sub-agents through a 6-phase workflow with file-based artifacts.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-orchestrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-orchestrate
Source: https://github.com/antigravityos187-sketch/universal-or-strategy/tree/main/.bob/skills/epic-orchestrate
Command: npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-orchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bob Shell, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing complex, multi-agent workflows, ensuring seamless coordination and execution of tasks across various phases.

Core Features & Use Cases

  • Multi-Agent Orchestration: Coordinate specialized sub-agents through a 6-phase epic workflow.
  • Phase-specific Execution: Each phase is executed by a dedicated sub-agent with appropriate capabilities.
  • File-based Artifacts: Pass artifacts via file system for each phase, ensuring a clear trail of progress.
  • Progress Reporting: Report progress to the user after each phase completes.
  • Manifest Management: Update and manage the manifest.json file for tracking phase status and artifacts.

Quick Start

Orchestrate the execution of the epic with ID '12345' by running the epic-orchestrate skill.

Frequently Asked Questions about epic-orchestrate

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

FAQPage Schema
How do I coordinate multi-agent workflows for complex task execution?

Multi-agent workflows are coordinated through a 6-phase protocol that assigns dedicated sub-agents to execute specific tasks, pass file-based artifacts, and report progress after each phase completes.

What is the best way to manage epic workflows involving multiple specialized sub-agents?

Epic management is handled by orchestrating specialized sub-agents across a structured 6-phase protocol, tracking phase status and artifacts by updating a manifest.json file.

How does file-based artifact passing work in multi-agent orchestration?

File-based artifact passing works by having each dedicated sub-agent generate outputs to the file system during its phase, creating a clear progress trail tracked within the manifest.json file.

Do I need Bob Shell to orchestrate complex multi-agent workflows?

Yes, Bob Shell is required because this orchestration relies on its sub-agent capabilities and file-based artifact management to execute the 6-phase epic workflow protocol.

Can I use this multi-agent orchestration for administrative workflow management?

Yes, this orchestration supports administrative workflows involving multi-agent coordination by managing task execution, artifact passing, and progress reporting across its 6 phases.

What are the limitations of using a 6-phase protocol for task coordination?

The 6-phase protocol requires Bob Shell sub-agent capabilities and depends entirely on file-based artifact management, meaning it is unsuitable for environments lacking file system access or sub-agent support.