spec-kitty-orchestrator-api-operator

# spec-kitty-orchestrator-api-operator Teach agents and external systems how to use `spec-kitty orchestrator-api` to drive workflows from outside the host CLI. The orchestrator-api is the only supported entry point for external automation -- direct frontmatter mutation, git worktree manipulation, or internal CLI internals are not part of the contract. --- ## When to Use This Skill - Build an external orchestrator that drives spec-kitty workflows - Integrate CI/CD pipelines with spec-kitty state transitions - Query mission and work package state from an external tool - Understand the boundary between host CLI and external API Do NOT use when the caller is an agent inside the host CLI (use `spec-kitty next`), wants setup/repair (use setup-doctor), or wants mission sequencing (the state machine owns that). --- ## How the Orchestrator API Works The orchestrator-api is a **stable JSON contract** — every command returns a canonical JSON envelope. External systems parse `success` first, then `error_code` for programmatic handling, then `data` for command-specific results. No command returns prose or mixed text/JSON. ### JSON Envelope (All Commands) ```json { "contract_version": "1.0.0", "command": "orchestrator-api.<subcommand>", "timestamp": "2026-03-22T10:00:00+00:00", "correlation_id": "corr-<uuid>", "success": true, "error_code": null, "data": { ... } } ``` - `success=true` → `error_code` is always `null` - `success=false` → `error_code` is a machine-rea...