mb-orchestrator

Classify mb-* task requests and route them to agent pipelines.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mb-orchestrator
Source: https://github.com/Yanick-mj/mb-framework/tree/main/agents/orchestrator
Command: npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cognitive orchestrator that classifies incoming mb-* task requests, routes them to the appropriate agent pipelines, and centralizes handoff and cost-tracking to maximize automation reliability.

Core Features & Use Cases

  • Task classification and routing to the correct agent pipeline based on the task class.
  • Context assembly, handoff between agents, and centralized cost logging across the orchestration lifecycle.
  • Enforcement of routing rules and design-system gates to prevent unsafe or conflicting executions.
  • Supports downstream agents including lead-dev, be-dev, fe-dev, ux-designer, architect, verifier, tea, pm, sm, quick-flow, devops, tech-writer.

Quick Start

Describe the task and let mb-orchestrator classify, route to the proper pipeline, and manage handoffs.

Frequently Asked Questions about mb-orchestrator

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

FAQPage Schema
How do I route incoming task requests to the correct agent pipeline automatically?

An orchestrator classifies incoming task requests and routes them to the appropriate agent pipeline automatically. It manages context assembly, handoffs, and enforces routing rules to ensure reliable execution across the orchestration lifecycle.

How do I track costs and manage context handoffs across multiple agents?

Centralize cost logging and manage context handoffs by using a cognitive orchestrator. It coordinates the orchestration lifecycle, ensuring reliable automation through controlled context assembly and cost tracking across multiple downstream agents.

What is task classification and routing in an mb-framework orchestration pipeline?

Task classification and routing in an orchestration pipeline involves categorizing incoming requests and directing them to specialized downstream agents. This enforces design-system gates and safety constraints to prevent unsafe or conflicting executions.

Can I enforce design-system gate conditions and safety constraints during agent handoffs?

Yes, an orchestrator enforces routing rules, design-system gate conditions, and safety constraints during agent handoffs. This prevents unsafe or conflicting executions across pipelines throughout the orchestration lifecycle.

What downstream agents can I route tasks to using a cognitive orchestrator?

You can route tasks to downstream agents including lead-dev, be-dev, fe-dev, ux-designer, architect, verifier, tea, pm, sm, quick-flow, devops, and tech-writer. The orchestrator manages handoffs and cost logging for these pipelines.

When should I not use a centralized orchestration pipeline for task routing?

Avoid centralized orchestration pipelines when tasks bypass design-system gate conditions or require executions conflicting with established safety constraints. The orchestrator enforces these routing rules strictly to maintain automation reliability.