rcode-raees-orchestrator

Build execution dispatch plans with owners, dependencies, and parallel blocks.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-raees-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-raees-orchestrator
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/agents/raees-orchestrator
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-raees-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity from complex requests by turning them into clear execution plans with one primary owner, explicit dependencies, and coordinated handoffs.

Core Features & Use Cases

  • Agent dispatching: Routes each request to the most appropriate specialist or specialist chain.
  • Execution sequencing: Determines what must happen first, what can run in parallel, and where blocking gates are needed.
  • Escalation handling: Sends strategic or cross-domain decisions to the council instead of forcing a premature decision.
  • Use Case: A user asks for a feature that touches design, frontend, backend, testing, and release management, and Raees produces a step-by-step dispatch plan with ownership and order.

Quick Start

Ask Raees to build a dispatch plan for your multi-step request and wait for the sequenced handoff plan.

Frequently Asked Questions about rcode-raees-orchestrator

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

FAQPage Schema
How do I sequence multi-agent handoffs for complex cross-domain requests?

Multi-agent handoffs are sequenced by analyzing team roles and dependency ordering to produce a dispatch plan. This plan defines a primary owner, a blocked-by chain, and parallel work blocks for coordinated execution.

What is task parallelization and how does it work in multi-agent orchestration?

Task parallelization in multi-agent orchestration is the process of identifying independent work blocks that can run simultaneously. It requires reading project state and dependency ordering to separate parallel tasks from those requiring sequential gating.

Can I use workflow planning to coordinate frontend, backend, and testing tasks?

Yes, workflow planning can coordinate frontend, backend, and testing tasks. It maps cross-domain requests to specialist agents, determining execution sequencing, explicit dependencies, and blocked-by chains for each phase.

What's the best way to assign a primary owner for multi-step engineering requests?

The best way to assign a primary owner is by building an execution dispatch plan. This plan evaluates team roles, current project state, and dependency ordering to designate a clear primary owner and explicit handoffs.

When should cross-domain decisions be escalated instead of forcing a single agent dispatch?

Cross-domain decisions should be escalated when they are strategic and require broader input. Escalation handling sends these decisions to the council instead of forcing a premature single-agent dispatch.