agent-teams-driven-development

Name: agent-teams-driven-development
Availability: InStock
Author: citybear3

Coordinate implementer and reviewers to execute plan tasks with iterative fix loops.

Updated Nov 4, 2022

Search Tags:#code review #workflow automation #Claude Code #agent orchestration #test-driven development #task planning #spec compliance

Ready to run

npx skills add https://github.com/CityBear3/dotfiles --skill agent-teams-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-teams-driven-development
Source: https://github.com/CityBear3/dotfiles/tree/main/claude/skills/agent-teams-driven-development
Command: npx skills add https://github.com/CityBear3/dotfiles --skill agent-teams-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you reliably implement plan-driven changes by coordinating an implementer with independent spec-compliance and code-quality reviewers, reducing missed requirements and quality regressions.

Core Features & Use Cases

Coordinated team execution: Runs each plan task with an implementer plus two parallel reviewers (spec compliance and code quality), including re-review loops until both approve.
Spec-first verification: The spec reviewer validates “nothing missing, nothing extra” by comparing the actual diff to the task spec.
Quality-first engineering discipline: The code quality reviewer enforces organization, naming, maintainability, and test discipline without re-litigating spec.
Plan/task orchestration: Uses Claude Code’s team orchestration (TaskList + SendMessage) and requires an isolated workspace before running.

Quick Start

In your workflow, invoke /execute-plan to run the plan through this team-based implementation and review loop.

Frequently Asked Questions about agent-teams-driven-development

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

FAQPage Schema

How do I automate code review and spec compliance for multi-step feature delivery?▼

You can automate code review and spec compliance by orchestrating an agent team with an implementer plus independent spec-compliance and code-quality reviewers. This coordinates iterative feature delivery where each task is implemented, reviewed, and re-reviewed after fixes until both reviewers approve.

How does agent orchestration work for test-driven development workflows?▼

Agent orchestration for test-driven development uses Claude Code's TaskList tracking and SendMessage coordination to manage an implementer and parallel reviewers. The workflow applies iterative fix loops per task, ensuring code quality and spec compliance before moving to the next planned task.

Can I use Claude Code team orchestration to verify nothing is missing or extra in a code diff?▼

Yes, Claude Code team orchestration supports spec-first verification where a spec reviewer validates the actual diff against the task spec. This ensures nothing missing and nothing extra by running parallel reviewer workflows per task alongside a code quality reviewer.

Do I need an isolated workspace before running agent-driven task planning and review loops?▼

Yes, you need an isolated workspace before running the agent-driven task planning and review loops. The coordinated team execution requires Claude Code team orchestration to manage TaskList tracking and SendMessage coordination across the implementer and independent reviewers.

What is the best way to enforce code quality and spec compliance in parallel during feature implementation?▼

The best way to enforce code quality and spec compliance in parallel is using a two-stage agent review system. A spec reviewer checks for missing or extra requirements while a code quality reviewer enforces organization, naming, and test discipline without re-litigating spec.

When should I not use agent teams driven development for workflow automation?▼

You should not use agent teams driven development for workflow automation if your project lacks explicit task specs or multi-step plans. The iterative fix loops require defined specs to validate diff compliance and coordinate the implementer plus two independent reviewers.