main-orchestrator

Decompose high-level requirements into epics and cross-domain tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Brownbull/ayni_core --skill main-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: main-orchestrator
Source: https://github.com/Brownbull/ayni_core/tree/main/.claude/skills/main-orchestrator
Command: npx skills add https://github.com/Brownbull/ayni_core --skill main-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes high-level requirements into epics and tasks and coordinates cross-domain orchestration to align frontend, backend, data, and devops.

Core Features & Use Cases

  • Epics decomposition: transforms high-level requirements into an epic with tasks and dependencies.
  • Cross-domain coordination: routes tasks to frontend, backend, data, test, and devops orchestrators.
  • Progress tracking and governance: maintains epic progress, resolves cross-domain conflicts, ensures quality gates.

Quick Start

Provide a PRD or feature request to the skill and it will generate an epic with tasks across domains.

Frequently Asked Questions about main-orchestrator

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

FAQPage Schema
How do I decompose a PRD into cross-domain tasks for frontend and backend?

To decompose a PRD into cross-domain tasks, provide the high-level requirements to generate an epic plan with domain-specific tasks for frontend, backend, data, and devops. It structures contexts, dependencies, and success criteria.

What is cross-domain orchestration in project planning?

Cross-domain orchestration in project planning coordinates task decomposition across multiple domains like frontend, backend, data, and devops. It aligns these domains by routing tasks to specific orchestrators and maintaining epic progress.

Can I use this for epic management across data and devops teams?

Yes, you can use this for epic management across data and devops teams. It transforms high-level feature requests into an epic with tasks and dependencies, ensuring progress tracking and governance across all involved domains.

How do I resolve cross-domain conflicts during epic decomposition?

To resolve cross-domain conflicts during epic decomposition, the orchestration process maintains epic progress, applies quality gates, and coordinates dependencies across frontend, backend, data, and test domains to ensure alignment.

Does this work for feature requests that span multiple domains?

Yes, this works for feature requests that span multiple domains. It applies orchestration standards to produce an epic plan with domain-specific tasks, satisfying specifications for task structure, contexts, dependencies, and success criteria.

What is the best way to structure dependencies in an epic plan?

The best way to structure dependencies in an epic plan is by decomposing high-level requirements into an epic with tasks and dependencies, ensuring cross-domain coordination and quality gates across frontend, backend, data, and devops.