role-orchestrator

What This Skill Does

The role-orchestrator is a sophisticated multi-agent management system designed to transform complex, multi-step user requirements into structured execution plans. By implementing a hierarchical orchestrator-worker pattern, it acts as the primary coordinator for the OpenClaw agent ecosystem. It delegates tasks to specialized agents—including PM, Architect, Tech Lead, DevOps, and Security—ensuring that large-scale development projects are broken down into logical, manageable segments. The skill automates the administrative overhead of organizing project files by enforcing a mandatory directory structure through its 'increment' system, ensuring that every project phase is logged, versioned, and audit-ready.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-role-orchestrator Once installed, ensure your project directory has been initialized with specweave init to allow the orchestrator to create the necessary .specweave/increments/ structure. This setup is a prerequisite for tracking the hierarchical execution of your development tasks.

Use Cases

This skill is ideal for:

• Full-stack SaaS Development: Orchestrating the entire lifecycle from initial product requirements (PM) to deployment (DevOps).
• Security-Critical Implementations: Coordinating between Security, Tech Lead, and Backend agents to ensure robust threat modeling and compliance.
• Complex Refactoring: Managing a Tech Lead and QA agents to verify stability across large codebases.
• Rapid Prototyping: Automating the setup of multi-agent workflows where parallel execution of Frontend and Backend tasks is required.

Example Prompts

1. "I need to build a secure subscription-based SaaS platform for inventory management. Please coordinate the team to handle the product strategy, system architecture, and initial security design."
2. "We need to implement a real-time messaging feature. Use the orchestrator to manage the architect, backend, and frontend agents to build the chat engine in parallel."
3. "Our current architecture is hitting performance bottlenecks. Please orchestrate a performance optimization sprint involving the Tech Lead, Backend, and DevOps agents."

Tips & Limitations

• The orchestrator works best when the user provides high-level project goals rather than granular command-level instructions.
• Always adhere to the 'Phase 0' rule: ensure the increment structure is established before triggering individual agents to avoid workspace clutter.
• The orchestrator acts as a coordinator; ensure you have the required individual agents installed in your registry for the orchestrator to delegate effectively.
• Avoid nested spawning; keep agent invocations in the main context to maintain visibility and control over the execution logs.