team:agile-dev

Orchestrate a 5-agent TDD team to automate story delivery from fetch to pull request.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill team-agile-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team:agile-dev
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/team%3Aagile-dev
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill team-agile-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire process of taking a story from "Ready" to "Done" by orchestrating a 5-agent TDD team, ensuring consistent quality and rapid delivery.

Core Features & Use Cases

  • Coordinated Team Workflow: Manages a PM, Architect, Test Architect, Backend Dev, and Frontend Dev through a structured TDD process.
  • Automated Story Lifecycle: Fetches stories, designs implementation, writes failing tests, implements code, and creates pull requests.
  • Use Case: Kick off a new feature development by invoking this skill, and it will manage the entire TDD cycle, from initial design to a ready-to-review pull request, minimizing manual oversight.

Quick Start

Invoke the agile dev team skill to start developing the next story.

Frequently Asked Questions about team:agile-dev

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

FAQPage Schema
How do I automate agile story delivery with a TDD team workflow?

Automated TDD story delivery orchestrates a 5-agent team (PM, Architect, Test Architect, Backend Dev, Frontend Dev) to handle the entire workflow from fetching stories to creating pull requests, minimizing manual oversight.

What roles are included in an automated TDD developer workflow?

An automated TDD workflow coordinates a 5-agent team comprising a PM, Architect, Test Architect, Backend Dev, and Frontend Dev to manage the structured TDD process from story design to pull request.

How does automated test-driven development work for feature implementation?

Automated test-driven development works by having agents design the implementation, write failing tests, and implement code to pass those tests, ensuring consistent quality before generating a ready-to-review pull request.

Do I need pre-defined agent configurations to automate pull request creation?

Yes, automating pull request creation requires pre-defined agent configurations and specific skills like /fetch-story and /pr to manage state transitions and communication between agents.

Can I use this agile team automation for both backend and frontend development?

Yes, this agile team automation supports both backend and frontend development by orchestrating dedicated Backend Dev and Frontend Dev agents within the TDD team to implement the full feature.

What are the limitations of orchestrating a 5-agent TDD team?

Orchestrating a 5-agent TDD team is limited by its strict dependency on pre-defined agent configurations and specific external skills like /fetch-story and /pr to execute the automated story lifecycle.