orchestrator-main

Orchestrate multi-agent OpenSpec development workflows across lifecycle stages in Cursor.

17|6|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/gmf520/openspec-agents --skill orchestrator-main
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-main
Source: https://github.com/gmf520/openspec-agents/tree/main/.cursor/skills/orchestrator-main
Command: npx skills add https://github.com/gmf520/openspec-agents --skill orchestrator-main

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of reliably orchestrating multiple specialized agents in Cursor to complete a full, stage-based software development lifecycle with consistent inputs, outputs, and workflow transitions.

Core Features & Use Cases

  • Cursor-first orchestration layer: Routes work to the correct sub-agent types using Cursor Task scheduling, while injecting the shared agent instructions as a prompt payload.
  • Stage-aware agent body mapping: Selects the correct agent body templates for CREATE, GATE_REVIEW, APPLY, CODE_REVIEW, TEST, VERIFY, and ARCHIVE so each phase follows the intended protocol.
  • Wave-based APPLY coordination: Implements group/Wave-style execution patterns for code changes, including a FINAL aggregation step.

Use case example: You want to use a standardized OpenSpec workflow to go from a change request to an implemented change set, including gate review, tests, verification, and final archive, with consistent per-stage agent behavior.

Quick Start

Use the Cursor orchestrator-main skill to run a full development session for a specific Change Name.

Frequently Asked Questions about orchestrator-main

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

FAQPage Schema
How do I coordinate multiple Cursor agents for a staged development workflow?▼

Multi-agent orchestration in Cursor routes work to specific sub-agent types via Cursor Task scheduling while injecting shared agent instructions as prompt payloads. This ensures consistent inputs and outputs across all lifecycle stages.

What is wave-based apply sequencing in multi-agent task scheduling?▼

Wave-based apply sequencing is a group execution pattern for code changes where tasks are dispatched in coordinated waves. It includes a FINAL aggregation step to merge outputs from multiple agents into a single implemented change set.

Can I use OpenSpec lifecycle stages like gate review and code review with Cursor agents?▼

Yes, OpenSpec lifecycle stages map directly to Cursor agents using stage-aware agent body templates. This routes tasks for CREATE, GATE_REVIEW, CODE_REVIEW, TEST, VERIFY, and ARCHIVE to follow the intended protocol for each phase.

Do I need prompt injection to run a full multi-agent OpenSpec workflow in Cursor?▼

Yes, prompt injection of shared agent body templates is required to run a full OpenSpec workflow in Cursor. It ensures each sub-agent receives the correct instructions to execute its designated lifecycle stage accurately.

How do I map subagent types to specific workflow stages like CREATE and VERIFY in Cursor?▼

You map subagent types to workflow stages by selecting the correct agent body templates for each phase. The orchestrator dispatches tasks by subagent_type, ensuring CREATE, APPLY, VERIFY, and other stages follow their specific protocols.