team-implement-plan-full

Team Implement Plan Full (Large Team)

Overview

This skill executes implementation plans with maximum parallelism. Each phase gets a dedicated implementer teammate. Independent phases run simultaneously within waves. A shared Reviewer provides cross-phase quality checks.

Team composition:

• phase-N-impl (one per phase in current wave): Implements their phase directly
• reviewer: Shared across all phases. Reviews FIFO as phases complete. Checks cross-phase consistency
• Lead: Orchestrates waves, manages team lifecycle, handles plan sync and completion

When to use this:

• Plans with 4+ phases where some phases are independent
• Large features spanning multiple modules/layers
• When speed of execution matters and you can afford the token cost

Token cost: ~100-150K per wave (scales with concurrent implementers)

References:

• references/team-lifecycle.md for team lifecycle pattern
• references/quality-pipeline-distribution.md for pipeline distribution

Initial Response

When invoked with a plan path:

"I'll set up a full implementation team with parallel execution. Let me read the plan, analyze the dependency graph, and present the execution waves before starting."

Workflow

Phase 1: Plan Analysis

Step 1a: Read and validate the plan

Read($0)  # Plan path from argument

Validate:

• Implementation phases with objectives and tasks
• Exit conditions per phase
• Dependencies between phases (from TaskList or plan structure)

Step 1b: Check existing progress

TaskList  # Check for existing tasks

If tasks exist with some completed, resume from current state (skip completed phases, adjust waves).

Step 1c: Build dependency graph

Parse phase dependencies to build execution waves:

Algorithm:
1. Read all tasks and their blockedBy relationships
2. Wave 1 = phases with no dependencies (blockedBy is empty)
3. Wave 2 = phases whose ALL dependencies are in Wave 1
4. Wave N = phases whose ALL dependencies are in Waves 1..N-1
5. Apply file conflict detection (Step 1d)