main-orchestratorlisted

# 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: ```yaml epic: id: "epic-{feature-name}" priority: "critical|high|medium|low" contexts: ["frontend", "backend", "data"] tasks: - task-001 - task-002 dependencies: {} success_criteria: "measurable outcomes" ``` ### Step 3: Decompose into Tasks For each task, use this template: ```yaml task: id: "task-{number}-{feature}" epic: "parent-epic-id" context: "frontend|backend|data|devops" when: "Start conditions" who: "domain-orchestrator-skill" where: "Code locations" what: "Feature description" how: "s