orchestrator

Routes project requests through a six-phase workflow to specialist skills.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill orchestrator-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/orchestrator
Command: npx skills add https://github.com/rhorba/RestoLedger --skill orchestrator-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-disciplinary software work (planning, design, coding, testing, shipping) without a clear process leads to skipped steps, missed requirements, and wasted context tokens. This Skill acts as the entry point for any project request, routing work to the right specialist skills and enforcing a consistent workflow. ## Core Features & Use Cases - Six-Phase Workflow: Enforces UNDERSTAND, BRAINSTORM, PLAN, EXECUTE, VERIFY, and SHIP phases with mandatory logging, an 80% test coverage gate, and git push at sprint close. - Specialist Routing: Maps request types (bug fix, new feature, security audit, marketing launch, database design) to 20+ specialist skills such as PM, Scrum Master, Software Architect, DBA, Tester, and DevOps. - Document-First Foundation: Generates PRD, system design, architecture, security, database, UX/UI, test strategy, and DevOps documents before any code on new projects. - Use Case: Start a new web app project and have the orchestrator collect environment variables, produce all foundation documents in docs/, commit them, then execute stories batch by batch with coverage enforcement. ## Quick Start Ask the assistant to start a new project or plan a feature, and the orchestrator will begin with the UNDERSTAND phase and route work to the right specialists.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I start a new software project with an AI team workflow?

Invoke the orchestrator at session start with your project idea. It runs an UNDERSTAND phase to scope the work, collects required environment variables, then generates foundation documents (PRD, architecture, security, database, UX, test strategy) before any code is written.

What is a document-first development workflow?

Document-first development produces a PRD, system design, architecture, security baseline, database schema, UX/UI foundations, test strategy, and stories before coding begins. Each document feeds the next, creating traceability from requirement to story to test to code.

How does the orchestrator decide which specialist skill to load?

It uses a routing table that maps request types to specialists. For example, bug fixes route to Tech Lead and Tester, database work routes to the DBA, and new projects route through PM, System Designer, Software Architect, and Scrum Master.

Does this workflow enforce test coverage requirements?

Yes. Before the SHIP phase, it runs a coverage report and requires at least 80 percent combined unit and integration coverage. If coverage falls below the threshold, tests must be written before proceeding.

When should I skip the full document chain?

Skip the chain for small tasks under one day, such as bug fixes or quick features. Medium features use a scope note and single ADR, while new projects and large features require the full PRD-to-stories artifact chain.

How does session resumption work between work sessions?

The orchestrator appends SESSION_START and SESSION_END entries to .logs/sessions.md. On return, it reads only the last SESSION_END entry to summarize prior state, then asks whether to continue or start fresh.