Skip to content
Skills Library
AI & agents · Automation

implement-team

/implement-team

Execute an implementation plan using parallel sub-agents for independent steps. Use when the user asks to "implement in parallel", "use a team to implement", or wants faster plan execution via agent team. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled.

Licence
MIT
Last repository change
14.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Execute an implementation plan using parallel sub-agents for independent steps. Use when the user asks to "implement in parallel", "use a team to implement", or wants faster plan execution via agent team. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled.

Triggers from the description

implement in paralleluse a team to implement
Original author description

Execute an implementation plan using parallel sub-agents for independent steps. Use when the user asks to "implement in parallel", "use a team to implement", or wants faster plan execution via agent team. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled.

How it works

  1. Phase 1 — Plan Analysis
  2. Phase 2 — Team Execution
  3. Phase 3 — Progress Tracking
  4. Phase 4 — Summary
  5. Constraints
Original SKILL.md headings · 64 lines, 430 words
SKILL.md preview
---
name: implement-team
description: Execute an implementation plan using parallel sub-agents for independent steps. Use when the user asks to "implement in parallel", "use a team to implement", or wants faster plan execution via agent team. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled.
disable-model-invocation: true
---

# Implement Team

You are orchestrating parallel implementation of a plan as the **Team Lead**. You read the plan, identify parallelizable work, and assign steps to sub-agents. You do not implement changes yourself.

## Phase 1 — Plan Analysis

Find and read the plan:

- If the developer specifies a file, use it.
- Otherwise, search for recent `plan-*.md` or implementation plan files.
- If multiple candidates exist, ask which one to use.

Analyze the plan steps:

1. Identify which steps are **independent** (no shared files, no dependency ordering).
2. Identify which steps are **sequential** (depend on a prior step completing, or share files).
3. Group independent steps into parallel batches.
4. Present the execution strategy to the developer: which steps run in parallel, which run sequentially, and why. Get confirmation before proceeding.

## Phase 2 — Team Execution

For each batch of independent steps:

1. Spawn one sub-agent (Sonnet) per step. Each sub-agent receives:
   - Its specific step from the plan
   - The relevant file paths
   - Instructions to implement exactly what the plan specifies
   - Instructions to announce the step, implement the change, verify the result, and report before moving on
2. **No two sub-agents write to the same file.** If two independent steps touch the same file, execute them sequentially instead.
3. Wait for all sub-agents in the batch to complete before starting the next batch.

For sequential steps:

- Execute one at a time, each in its own sub-agent.
- Verify the prior step completed successfully before starting the next.

## Phase 3 — Progress Tracking

Update the plan document as steps complete:

- `[ ] pending` to `[x] complete`
- If a step completes with caveats, add a "Notes:" line below the item.
- If a step fails, stop and report to the developer before continuing.

The plan document serves as the live progress tracker. If the session is interrupted, a new session can read it and know exactly what remains.

## Phase 4 — Summary

When all steps are complete, report:

- Total steps completed
- Steps that completed with notes
- Any new issues discovered during implementation (captured in a separate section, not acted on)

## Constraints

- **Delegate all implementation to sub-agents.** Do not implement changes directly.
- **Stay in scope.** Implement exactly what the plan specifies. New issues go in a report, not into the fix scope.
- **Do not commit.** The developer decides when to commit.
- **Do not deploy.** No deploy or push commands.

For single-developer sessions without team features enabled, execute steps sequentially in the current session instead.

Versions

The database has no other skills named implement-team.

Database snapshot: 13.11.2026 · package version 977aeedd30dc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100team-dev
    Use when executing an implementation plan in parallel with agent teams and quality gates. Spawns implementer teammates in split panes, orchestrated by a team lead who enforces spec compliance and code quality reviews.
  • 95plan-orchestrate
    Execute implementation plans with parallel TDD workers. Use when ready to run, execute, or start a plan. Triggers on "run the plan", "execute the plan", "implement the plan", "start the plan", "start implementation", "orchestrate", "begin autonomous execution". Requires a plan…
  • 100task-writing
    Use when writing an implementation plan for a multi-step job, or when preparing a task text for an agent (scout, reviewer, maintainer); especially if parallel work is to be given to more than one agent. The main chat (central agent) loads it.
  • 90implement
    Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.
  • 100team-implement
    承認済みの実装計画(Plan)を Agent Team で並列に実装するスキル。 Plan をタスクに分割 → 依存関係を設定 → Wave ごとに並列エージェントを起動 → 完了を待って次の Wave → 最後にビルド&テスト検証。 team-plan スキル(調査→計画)の後に使う「実装実行フェーズ」。 Use when: 計画を並列に実装したい、チームで実装を進めたい、 Wave 実行で効率よくコードを書きたい。 Triggers: "team implement", "チームで実装", "並列実装", "plan を実装して", "wave…
  • 100execute
    Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.