What problem does it solve? Multi-file feature implementation often burns tokens on unnecessary agent spawns, redundant reviews, and mid-flight clarification rounds. This Skill executes a finished spec's Team Orchestration Plan with disciplined wave-based execution, keeping orchestrator, executor, and verifier roles separate and costs under control. ## Core Features & Use Cases - Wave-based execution: Groups spec steps into waves scoped by verification gates, with one executor agent per wave and one commit per wave as a rollback checkpoint. - Budget-disciplined verification: Dispatches a minimal set of parallel code-review verifiers per wave using a routing table, and spot-checks small deterministic fixes instead of re-spawning reviewers. - Feedback loops to green: Consolidates verifier findings by severity and iterates with the executor in its existing thread until all Critical findings are resolved. - Use Case: You have a finished spec at workspace/spec/chat-constraints-spec.md and want it implemented across backend, frontend, and tests with verified gates at each stage, without wasting tokens on ad-hoc agent orchestration. ## Quick Start Implement the spec at workspace/spec/chat-constraints-spec.md by running its orchestration plan wave by wave.
