team-implement-plan

Team Implement Plan (Small Review Team)

Overview

This skill executes implementation plans using a small team of 2-3 members. Unlike the solo implement-plan which uses an orchestrator/subagent pattern, this skill has teammates that implement code directly and review each other's work adversarially.

Team composition:

• Implementer: Writes code directly using Write/Edit/Bash. Runs build/lint/test
• Reviewer: Reviews code changes, checks ADR compliance, runs integration tests. Sends fix requests
• Integrator (optional, for plans with 4+ phases): Monitors cross-phase consistency, handles plan sync

When to use this vs implement-plan:

• Use implement-plan for simple plans (1-3 phases, clear requirements, ~30-40K tokens/phase)
• Use team-implement-plan for quality-sensitive plans where adversarial review matters (~60-80K tokens/phase)
• Use team-implement-plan-full for large plans with parallel phases (~100-150K tokens/wave)

Reference: See references/team-lifecycle.md for team lifecycle and references/quality-pipeline-distribution.md for pipeline distribution.

Initial Response

When invoked with a plan path:

"I'll set up a small implementation team. An Implementer will write code while a Reviewer independently checks quality. Let me read the plan and set up the team."

Workflow

Phase 1: Plan Reading & Team Setup

Step 1a: Read and validate the plan

Read($0)  # Plan path from argument

Validate the plan has:

• Implementation phases with objectives
• Tasks per phase
• Exit conditions per phase
• Dependencies between phases

If the plan is missing required sections, inform the user and stop.

Step 1b: Check existing progress

TaskList  # Check for existing tasks from this plan

If tasks exist with some completed, resume from the first incomplete phase. If no tasks exist, the plan was created without task bootstrapping — create tasks now.

Step 1c: Determine team size

Plan Size	Team
1-3 phases	Implementer + Reviewer (2 members)
4+ phases	Implementer + Reviewer + Integrator (3 members)