orchestrator

Coordinate end-to-end software development workflows across heterogeneous projects.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill orchestrator-sfzmango
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/Sfzmango/Maungs-agentic-toolbelt/tree/main/plugins/maungs-agentic-toolbelt/skills/orchestrator
Command: npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill orchestrator-sfzmango

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating multi-phase software development workflows is time-consuming, inconsistent across projects, and prone to missed quality gates or approval steps, especially when adapting to unique project conventions and tooling.

Core Features & Use Cases

  • Specialized subagent delegation: Routes each phase of the dev cycle (planning, implementation, review, resolution) to purpose-built subagents (product owner, architect, developer, PR reviewer, resolution) to eliminate manual coordination overhead.
  • Auto-adaptation to project context: Automatically detects project conventions from AGENTS.md, plan files, package manifests, and pre-commit hook systems to work with any codebase without hardcoded configuration.
  • Built-in safety and quality guardrails: Enforces mandatory human approval checkpoints for commits and pushes, runs environment preflights for required tools like gh CLI and MCP servers, and supports local-only dry runs via the --experiment flag for safe testing. Use case: For example, invoke the skill with a GitHub issue ID to automatically generate a compliant plan, implement changes, run a full code review, and prepare a merge-ready PR with zero manual workflow coordination.

Quick Start

Use the orchestrator skill to run a full end-to-end development cycle for a GitHub issue ID or free-text project topic of your choice.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I automate end-to-end software development workflows from a GitHub issue?

Automating end-to-end software development workflows routes each phase to specialized subagents, detecting project conventions automatically to generate a plan, implement changes, perform a code review, and prepare a merge-ready PR.

Can I use subagent delegation for project automation without manual configuration?

Subagent delegation for project automation works without manual configuration by auto-detecting conventions from AGENTS.md, plan files, package manifests, and pre-commit hooks, adapting to heterogeneous codebases seamlessly.

Does GitHub PR management require human approval checkpoints during automated code reviews?

GitHub PR management enforces mandatory human approval checkpoints for commits and pushes, running environment preflights for required tools like gh CLI and MCP servers before finalizing the review.

What is the best way to test dev workflow orchestration safely before pushing changes?

Testing dev workflow orchestration safely is best achieved using the local-only dry run capability via the --experiment flag, allowing you to validate the full cycle without committing or pushing code.

How does subagent delegation work for routing different phases of a dev cycle?

Subagent delegation works by routing distinct development phases to purpose-built agents like product owner, architect, developer, PR reviewer, and resolution agents, eliminating manual coordination overhead across the workflow.

Do I need to install GitHub CLI and MCP servers for project automation?

Project automation requires GitHub CLI and MCP servers for issue and PR management, executing environment preflight validation checks to ensure all necessary dependencies are present before executing workflows.