What problem does it solve? Running a multi-phase agent workflow manually requires tracking which phase comes next, invoking the right agent, and detecting stalls or failures. This Skill automates that coordination by reading a persistent state file and dispatching the correct subagent until the workstream completes. ## Core Features & Use Cases - State-driven dispatch: Reads .spae/current/STATE.json to resolve the current phase and spawns the matching subagent (spec, plan, inspect, build, check, fix, verify) in a loop. - Failure-safe halting: Stops immediately on subagent failure, stalled phases, unknown phase values, or a missing workstream, preventing runaway execution. - Read-only orchestration: Performs no file writes itself; all state mutations are delegated to subagents, keeping responsibilities cleanly separated. - Use Case: You have a feature proposal and want the full SPAE pipeline executed autonomously. Invoke the orchestrator with the proposal, and it bootstraps the spec phase, then loops through plan, inspect, build, check, fix, and verify until the workstream reaches done. ## Quick Start Ask the agent to orchestrate the SPAE workflow for your proposal, for example: run the SPAE orchestrator with the proposal to add user authentication to the API.
