Verified:GitHub

team-implement

Orchestrate parallel subagent implementation across modules with defined file ownership.

3|1|Updated Feb 7, 2026

Search Tags:#tdd #feature development #parallel development #code implementation #adversarial review #subagent coordination

Ready to run

npx skills add https://github.com/yon/agentic-dev-os --skill team-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-implement
Source: https://github.com/yon/agentic-dev-os/tree/main/.claude/skills/team-implement
Command: npx skills add https://github.com/yon/agentic-dev-os --skill team-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines complex feature development by enabling multiple AI agents to work on different parts of a codebase simultaneously, followed by integrated review.

Core Features & Use Cases

Parallel Development: Assigns distinct file ownership to multiple "production-code-engineer" subagents for concurrent implementation.
Dependency Management: Handles sequential execution for dependent tasks (e.g., integration after module completion).
Adversarial Review: Ensures code quality through separate review subagents (code, security, tests) that do not edit code.
Use Case: Developing a new microservice with a distinct API, business logic, and data access layer, where each layer can be worked on independently by different agents.

Quick Start

Use the team-implement skill to spawn parallel implementation subagents for modules X and Y, followed by integration and review.

Frequently Asked Questions about team-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement feature development across multiple modules in parallel?▼

Parallel feature development is orchestrated by assigning distinct file ownership to multiple subagents for concurrent implementation, followed by sequential task dependency management, integration, and adversarial review.

How does adversarial review work for concurrent code implementation?▼

Adversarial review for concurrent code implementation uses separate specialized subagents to review code, security, and tests without directly editing the code, ensuring quality and adherence to conventions.

Can I use subagent coordination to manage task dependencies during TDD?▼

Subagent coordination manages task dependencies during TDD by executing dependent tasks sequentially, such as running integration only after module completion, while ensuring test-driven development compliance.

What is the best way to structure microservice development with independent layers?▼

Microservice development with independent layers is structured by assigning distinct API, business logic, and data access layers to different subagents to work on simultaneously, followed by integrated review.

Does parallel subagent implementation enforce project conventions?▼

Parallel subagent implementation enforces project conventions by requiring each implementation subtask to adhere to defined project conventions while ensuring test-driven development compliance.

Why are separate review subagents used instead of the implementation agents?▼

Separate review subagents are used instead of implementation agents because they do not edit code, ensuring objective adversarial review for code quality, security, and tests without development bias.