What problem does it solve? Coordinating multi-agent implementation work is error-prone: agents get spawned in the wrong order, PRs skip review, and work lands directly on shared branches. This Skill turns an approved plan into a disciplined team execution with enforced roles, gates, and review cycles. ## Core Features & Use Cases - Ordered agent spawning: Spawns a Principal Engineer, then a QA Engineer, then up to 3 Workers in a mandatory order, each with a defined model tier and dispatch contract. - Worktree isolation with hard gates: Creates one git worktree per task and refuses to run if the branch is more than 50 commits behind the default branch or no plan exists. - Gated PR workflow: Workers open draft PRs only; QA runs CI-equivalent checks and is the sole agent allowed to promote a PR to ready after Principal Engineer review. - Use Case: After running team-plan for a gpu-scheduler-retry project, invoke this Skill to spin up the team, have Workers implement tasks via TDD in separate worktrees, and get reviewed, validated draft PRs promoted only after the full review cycle passes. ## Quick Start Run /team-execute with the project name of an existing plan in .agents/plans/ to spawn the agent team and begin implementation.
