skills.rest
marmelab
marmelabOFFICIAL
Explore all skills by this author →
WebsiteGitHub

agent-team

Coordinate multi-agent ticket execution with wave-level concurrency and a shared git merger.

26|4|Updated Apr 9, 2026
Search Tags:#code review#workflow orchestration#multi-agent#test validation#ticket implementation#git merging#session scoping
One-click install
npx skills add https://github.com/marmelab/crm-builder --skill agent-team-marmelab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-team
Source: https://github.com/marmelab/crm-builder/tree/main/claudeConfig/.claude/skills/agent-team
Command: npx skills add https://github.com/marmelab/crm-builder --skill agent-team-marmelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates a coordinated multi-agent workflow so complex CRM development tickets can be implemented, reviewed, tested, and merged with consistent peer-to-peer messaging inside one shared team.

Core Features & Use Cases

  • Wave-based ticket execution: Plans N tickets into a single concurrent “wave” with one shared merger to reduce git lock contention.
  • Strict role separation: Runs developers, quality reviewers, and test validators with enforced counterpart addressing per ticket.
  • Deterministic session scoping: Uses a mandatory tickets-<SESSION_SHORT_ID> team name to prevent cross-session collisions and misrouted messages.
  • Graceful teardown and recovery paths: Supports shutdown acknowledgements, safe team deletion gating, and clear failure/abort handling without killing healthy tickets.

Quick Start

Ask the orchestrator to handle a complex request by invoking the agent-team skill for the session-scoped wave of tickets, and it will create the team, dispatch developer/reviewer/test-validator agents, coordinate merging, then teardown after completion.

Frequently Asked Questions about agent-team

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

FAQPage Schema
How do I coordinate multi-agent workflows for parallel ticket implementation?▼

Multi-agent workflows for parallel ticket implementation are coordinated by dispatching developer, reviewer, and test validator agents into a single concurrent wave. This approach synchronizes the development flow and routes peer-to-peer messaging to prevent miscommunication.

What is the best way to prevent git index locking when running concurrent code reviews?▼

To prevent git index locking during concurrent code reviews, route all finalized branches through a single shared git-merger stage. This serialized merging step eliminates lock contention while processing multiple parallel work items.

Can I use a single shared peer team for test validation and ticket implementation across multiple sessions?▼

You cannot share a peer team across multiple sessions. The workflow requires a mandatory session-scoped team name formatted as tickets-<SESSION_SHORT_ID> to prevent cross-session collisions and ensure messages are strictly addressed per ticket.

How do I safely teardown a multi-agent team after workflow orchestration completes?▼

To safely teardown a multi-agent team after workflow orchestration, you must wait for shutdown acknowledgements from all active agents. The system uses this acknowledgement gating before executing TeamDelete to ensure healthy tickets are not prematurely killed.

Does wave-based ticket execution support failure and abort handling without killing healthy work items?▼

Wave-based ticket execution supports clear failure and abort handling that isolates unhealthy work items. It gracefully tears down failed agents while allowing healthy tickets to complete their synchronized developer, reviewer, and test validator flows.

When do I need strict role separation for developer and reviewer agents in a CRM development workflow?▼

Strict role separation for developer and reviewer agents is needed when complex CRM development requires deterministic quality control. Enforced counterpart addressing ensures every ticket passes through synchronized developer, reviewer, and test validator stages without overlapping responsibilities.

Related Skills

Explore More Software Engineering Skills→
ourinesourines
39

worktree-task

Launch background agent sessions for large coding tasks via git worktrees and tmux.

Community
Advanced
BedaBeda-GrowthBedaBeda-Growth

orchestrator-mode

Decompose complex plans into parallel waves with gate verification.

Official
Advanced
coff33ninjacoff33ninja

test-driven-development

Implement the Test-Driven Development cycle with failing tests before code.

Community
Intermediate
SteelMorganSteelMorgan
87

task-breakdown-linear

Generate a JSON task breakdown with dependencies and self-checks for linear execution.

Community
Intermediate