dev-orchestrator

Route development work through minimal skill sequences with plan-first gates.

Updated May 8, 2026

Search Tags:#workflow #planning #qa #handoff #orchestrate #route #multi-role

Ready to run

npx skills add https://github.com/ace3/skills --skill dev-orchestrator-ace3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-orchestrator
Source: https://github.com/ace3/skills/tree/main/skills/dev-orchestrator
Command: npx skills add https://github.com/ace3/skills --skill dev-orchestrator-ace3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill routes development work through a safe, minimal set of skills to preserve plan-first gates and avoid direct execution.

Core Features & Use Cases

Orchestrates multi-role planning by sequencing a minimal skill path (research, product-manager, engineering-manager, backend-developer, frontend-developer, qa, deployment-ops) without performing implementation.
Provides clear handoff inputs and outputs, gating decisions, and artifact routing to ensure auditability.
Useful for planning sessions, feature scoping, and risk assessment where cross-team coordination is required.

Quick Start

Route a feature task through the standard plan gates from product to engineering to QA without execution, returning the recommended next skill and full handoff sequence.

Frequently Asked Questions about dev-orchestrator

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

FAQPage Schema

How do I orchestrate multi-role development planning across product, engineering, and QA?▼

Multi-role development planning is orchestrated by routing work through a minimal skill sequence covering product management, engineering, backend, frontend, QA, and deployment, returning a routing bundle with the next skill, rationale, and approval gates.

What is the best way to sequence handoffs between backend and frontend without skipping plan-first gates?▼

Sequencing handoffs safely requires routing the development task through a predetermined skill path that enforces approval gates and stop conditions, ensuring backend and frontend transitions occur only after prior planning artifacts are approved.

Can I use workflow orchestration to coordinate cross-team feature scoping without executing implementation?▼

Workflow orchestration can coordinate cross-team feature scoping by generating a full sequence of required roles and gating decisions while explicitly avoiding direct execution of any engineering or implementation tasks.

How does skill routing handle security and monitoring tasks in a development pipeline?▼

Skill routing handles security and monitoring by including them in the full planning sequence alongside engineering and deployment, ensuring these tasks receive structured handoff inputs and are gated by predefined stop conditions.

Do I need to manually define approval gates when routing development work through multiple roles?▼

Approval gates are automatically provided within the routing bundle output, which details the chosen next skill, the full sequence, and the specific stop conditions required to preserve plan-first gates across multi-role scenarios.

What are the limitations of using an orchestrator for development work routing?▼

The orchestrator is limited to planning and routing; it does not perform execution or implementation, meaning users still need separate skills or teams to execute the actual research, engineering, and QA tasks defined in the routing bundle.