master-orchestrator

Coordinate multi-domain execution plans across Supabase, Node.js, React, Rust, and LLM workstreams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Large-scale full-stack requests demand manual orchestration of domain-specific skills, MCP connectivity, and QA gates, which leads to missed dependencies, unchecked tooling gaps, and token waste; the master orchestrator automates classification, decomposition, and verification so every parallel work stream stays aligned with the true system state.

Core Features & Use Cases

  • Domain classification matrix for Supabase, Node.js/Express, React/Next.js, Rust/Tauri, LLM pipelines, auth, fintech, QA, and other areas, mapping each request signal to the exact skill and MCP dependencies required.
  • Wave-based decomposition that enforces Phase 0 MCP checks, Phase 1 schema work, downstream type/service/frontend layers, QA/testing, and documentation, with dependency graphs, file ownership, and token budget discipline baked in.
  • MCP-aware QA cascade and status reporting that verifies MCP connectivity before work, runs skill-level QA gates, escalates integration and master-level checks, logs results in VERSION_LOG.jsonl, and keeps every agent accountable for MCP verification commands.
  • Use Case: When orchestrating a Supabase + Node.js + React feature with OAuth, fintech logic, and QA automation, the orchestrator routes schema work to supabase-db-architect, services to node-feature-scaffolder, UI to react-frontend, integration tests to bb-qa-gate, and documentation to doc-generator while managing MCP/tool health.

Quick Start

Use the master orchestrator to break your large full-stack request into waves with MCP checks, QA gates, and skill assignments.

Frequently Asked Questions about master-orchestrator

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

FAQPage Schema
How do I coordinate full-stack development across Supabase, Node.js, and React?

Coordinate full-stack execution by classifying domain signals and decomposing requests into sequential waves. This orchestrator maps schema, service, and frontend tasks to domain-specific skills while tracking dependencies and file ownership to keep parallel workstreams aligned.

How does wave-based decomposition manage parallel workstreams in enterprise environments?

Wave-based decomposition enforces phase sequencing starting with MCP checks, followed by schema work, downstream service layers, and QA gates. It tracks dependency graphs and file ownership to prevent conflicts across parallel enterprise workstreams.

Can I automate MCP tool connectivity checks and QA gates for multi-skill execution?

Yes, MCP-aware QA cascades verify tool connectivity before executing work and run skill-level QA gates afterward. Results are escalated through integration checks and logged in VERSION_LOG.jsonl to maintain agent accountability.

What is the best way to handle token discipline and degraded-mode fallbacks during large-scale orchestration?

Handle token discipline and degraded-mode fallbacks by applying automated classification and decomposition that monitors token budgets across waves. The orchestrator enforces fallback handling when MCP connectivity or tool verification fails.

Do I need existing domain-specific skills before using a master orchestrator for multi-domain execution?

You need domain-specific skills for Supabase, Node.js, React, or Rust to receive routed workstream assignments. The orchestrator classifies request signals and delegates to these skills rather than generating code directly.

When should I not use a master orchestrator for full-stack development?

Avoid using a master orchestrator for single-domain requests that do not span schema migrations, service scaffolding, frontend components, and QA gates. It is designed for large-scale multi-domain execution requiring wave dependencies and MCP verification.