orchestrator

Orchestrates the SDLC workflow by spawning sequential AI agents.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/VitorAndTxr/omni-sw --skill orchestrator-vitorandtxr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/VitorAndTxr/omni-sw/tree/main/skills/orchestrator
Command: npx skills add https://github.com/VitorAndTxr/omni-sw --skill orchestrator-vitorandtxr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SDLC Orchestrator — Manages the full Software Development Agency workflow end-to-end by spawning role-based agents in sequence across seven phases, enforcing gates and surfacing questions to the user.

Core Features & Use Cases

  • Spawns PM, PO, TL, Dev, and QA agents in Plan through Document phases to drive a project from objective to delivery.
  • Enforces gates, handles feedback loops, and produces timestamped artifacts for audit and traceability.
  • Suitable for teams needing automated, deterministic multi-agent SDLC execution with clear provenance.

Quick Start

Use the orchestrator to drive the full SDLC workflow by spawning PM, PO, TL, Dev, and QA agents in sequence.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I automate the full software development lifecycle with multi-agent workflows?

Multi-agent SDLC automation is handled by spawning phase-specific PM, PO, TL, Dev, and QA agents in a fixed sequence. The orchestrator enforces gate decisions and produces timestamped artifacts, creating a deterministic, repeatable workflow from project objective to final delivery.

What is state management's role in deterministic software project workflows?

State management in deterministic software workflows tracks live progress and artifacts across all phases. Persistent state ensures the multi-agent orchestration maintains context and provenance from initial planning through documentation, preventing data loss during sequential agent handoffs.

Can I use autonomous agents to enforce gates and handle feedback loops in software engineering?

Autonomous agents can enforce gates and handle feedback loops by operating within a fixed sequence across seven SDLC phases. The orchestrator surfaces questions to the user during these gated transitions, ensuring deterministic execution and clear audit trails.

Does the SDLC orchestrator support agent spawning for role-based development phases?

The SDLC orchestrator supports agent spawning by creating role-based PM, PO, TL, Dev, and QA agents sequentially. Each agent drives a specific phase from Plan through Document, executing automated tasks while maintaining persistent state and timestamped artifacts.

When do I need a fixed-sequence multi-agent workflow for software delivery?

A fixed-sequence multi-agent workflow is needed when software projects require deterministic, repeatable execution from objective to delivery. If your team needs automated phase-specific agents, enforced gates, and timestamped artifact tracking for audit, this approach provides clear provenance.