mcpField
T
team-iterdev

team-iterdev

github.com/catlog22Development2.1k45 installsUpdated 19w ago
Repository

About team-iterdev

team-iterdev is an iterative team development workflow skill. A coordinator selects a pipeline for the task and tracks progress, while developers and reviewers can run up to three generator-critic rounds and share learnings across tasks.

Key features

  1. 01Dynamic development pipeline selection
  2. 02Developer-reviewer iteration loop
  3. 03Real-time task ledger
  4. 04Shared cross-sprint learnings

Use cases

  1. 01Break development work into iterative steps
  2. 02Track team task progress
  3. 03Address implementation issues through review rounds

MCP support

Uses `mcp__ccw-tools__team_msg` as its team message bus.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/catlog22/claude-code-workflow --skill team-iterdev

After installing, type/team-iterdevin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

roles/architect/
role.md
roles/coordinator/
role.md
roles/coordinator/commands/
analyze.md
dispatch.md
monitor.md
roles/developer/
role.md
roles/reviewer/
role.md
roles/tester/
role.md
specs/
pipelines.md
team-config.json

Details

From the project README

Team IterDev

Iterative development team skill. Generator-Critic loops (developer<->reviewer, max 3 rounds), task ledger (task-ledger.json) for real-time progress, shared memory (cross-sprint learning), and dynamic pipeline selection for incremental delivery.

Architecture

Skill(skill="team-iterdev", args="task description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+
                    v       v       v       v
               [architect] [developer] [tester] [reviewer]
              (team-worker agents, each loads roles/<role>/role.md)

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
architectroles/architect/role.mdDESIGN-*false
developerroles/developer/role.mdDEV-*true
testerroles/tester/role.mdVERIFY-*false
reviewerroles/reviewer/role.mdREVIEW-*false

Role Router

Parse $ARGUMENTS:

  • Has --role <name> → Read roles/<name>/role.md, execute Phase 2-4
  • No --role → @roles/coordinator/role.md, execute entry router

Shared Constants

  • Session prefix: IDS
  • Session path: .workflow/.team/IDS-<slug>-<date>/
  • CLI tools: ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
  • Message bus: mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker Spawn Template

Coordinator spawns workers using this template:

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: "iterdev",
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: iterdev
requirement: <task-description>
inner_loop: <true|false>

Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

User Commands

CommandAction
check / statusView execution status graph
resume / continueAdvance to next step

Session Directory

.workflow/.team/IDS-<slug>-<YYYY-MM-DD>/
├── .msg/
│   ├── messages.jsonl          # Team message bus
│   └── meta.json               # Session state
├── task-analysis.json          # Coordinator analyze output
├── task-ledger.json            # Real-time task progress ledger
├── wisdom/                     # Cross-task knowledge accumulation
│   ├── learnings.md
│   ├── decisions.md
│   ├── conventions.md
│   └── issues.md
├── design/                     # Architect output
│   ├── design-001.md
│   └── task-breakdown.json
├── code/                       # Developer tracking
│   └── dev-log.md
├── verify/                     # Tester output
│   └── verify-001.json
└── review/                     # Reviewer output
    └── review-001.md

Specs Reference

Error Handling

ScenarioResolution
Unknown commandError with available command list
Role not foundError with role registry
GC loop exceeds 3 roundsAccept with warning, record in shared memory
Sprint velocity drops below 50%Coordinator alerts user, suggests scope reduction
Task ledger corruptedRebuild from TaskList state
Conflict detectedUpdate conflict_info, notify coordinator, create DEV-fix task
Pipeline deadlockCheck blockedBy chain, report blocking point

Comments

Markdown supported