master-orchestrator

Master Orchestrator

Purpose

Inspect project state and route to the correct skill. This skill NEVER implements, debugs, or designs. It only routes.

Agent Protocol

Trigger

Exact user phrases: "start", "help me build", "initialize", "I want to build X", "where do I start", "what skill", "what should I do next", "begin", "let's start".

Input Context

• Working directory must be set to the project root.
• If no project root is detectable, ask the user: "Where is your project directory?"

Output Artifact

None. This skill produces no files. It emits a routing decision as text.

Response Format

The agent MUST output exactly one of the following templates. No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. No explanations.

Skills are identified by their directory under skills/ (e.g. dev-loop/code-review = skills/dev-loop/code-review/SKILL.md); every route below uses that form. When a request matches nothing below, consult the Quick Map in .claude/rules/routing.md or list skills/<category>/.

Template A — Route to a single skill:

Next skill: **{category/skill-path}**
Reason: {one sentence exactly}
Context: {key facts the next skill needs}

Template B — Route to multiple skills (sequential):

Next skills:
1. **{category/skill-path}** — {reason}
2. **{category/skill-path}** — {reason}

Template C — Need more information:

Need: {what you need from the user}
Options:
- {option 1}
- {option 2}

Completion Criteria

This skill is complete when:

• Project state has been checked (docs/, README, package manifests)
• Stack/language detected or asked
• A single next skill has been identified
• Output follows exactly one of the three templates above
• No implementation, debugging, or advice has been given

Max Response Length

3 lines maximum for routing. 6 lines maximum for "need more information."

Workflow

Step 1: Check Filesystem

Run these checks in order. Stop at the first match. Use the host's file-listing/glob tool (or ls / PowerShell Test-Path — note -LiteralPath disables wildcards, so use -Path for globs):

1. docs/brief*.md — brief exists
2. docs/prd*.md — PRD exists
3. docs/decisions/ or docs/adr/ — ADRs exist
4. docs/specs/ — tech specs exist
5. package.json — Node project
6. Cargo.toml — Rust project
7. go.mod — Go project
8. requirements.txt or pyproject.toml — Python project
9. pom.xml, build.gradle or build.gradle.kts — JVM project