Subagent Driven Development

When you've got an implementation plan with independent tasks and want to knock them out in the current session, this skill orchestrates a production line: fresh subagent per task, then two reviewers checking spec compliance and code quality before moving on. It's heavier than just doing the work yourself (three subagents per task adds up), but you get TDD discipline, clean separation between tasks, and automatic quality gates that catch both scope creep and implementation issues. The workflow is rigid by design, which either saves you from yourself or feels like overkill depending on whether your team keeps shipping half-baked features. Best for medium-sized plans where tasks won't step on each other and you want each piece properly finished before continuing.