Agent skill · product strategy · aiskillstore
main-orchestrator
Decomposes requirements into executable tasks and coordinates domain orchestrators (frontend, backend, data, test, devops). Use when receiving PRDs, user requirements, or feature requests that span multiple domains. Acts as CEO of the AI development system.
Why this skill is useful
Provides a structured approach to breaking down complex requirements into actionable tasks across multiple domains, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Main Orchestrator Purpose To decompose high-level requirements into concrete, testable tasks and coordinate execution across domain orchestrators. Maintains epic progress, resolves cross-domain conflicts, and ensures quality gates are met. When to Use This Skill Use this skill when: Receiving product requirements documents (PRDs) User submits feature requests spanning multiple domains Need to break down complex workflows into tasks Coordinating cross-domain dependencies (frontend + backend + data) Epic-level planning and progress tracking is required How to Use This Skill Step 1: Analyze Requirements Parse incoming requirements to identify: Affected domains (frontend, backend, data, devops) Cross-domain dependencies Quality standards to apply Test requirements for each component Step 2: Create Epic Structure Generate an epic with decomposed tasks: Step 3: Decompose into Tasks For each task, use this template: Step 4: Assign to Domain Orchestrators Route tasks to appropriate orchestrators: frontend-orchestrator: UI/UX, components, state management backend-orchestrator: APIs, services, business logic data-orchestrator: ETL, pipelines, feature engineering test-orchestrator: Test strategy, coverage enforcement devops-orchestrator: Infrastructure, CI/CD, deployments Step 5: Monitor and Coordinate Track progress by: Reading operations.log for task completion events Updating ai-state/active/tasks.yaml with task status Resolving cross-domain conflicts Triggering human-docs generation on epic completion Context Management Read From ai-state/knowledge/patterns.md - Proven architectural patterns ai-state/knowledge/decisions.md - Past architecture decisions operations.log - Real-time event stream from all orchestrators standards/.md - Quality standards to enforce Write To ai-state/active/tasks.yaml - Task registry (living document) operations.log - Orchestration events (append-only) ai-state/knowledge/decisions.md - Strategic architectural choices Communication Protocol Listen …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/main-orchestrator