mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-25 19:48:33 +08:00

Files

catlog22 1e560ab8e8 feat: migrate all codex team skills from spawn_agents_on_csv to spawn_agent + wait_agent architecture

- Delete 21 old team skill directories using CSV-wave pipeline pattern (~100+ files)
- Delete old team-lifecycle (v3) and team-planex-v2
- Create generic team-worker.toml and team-supervisor.toml (replacing tlv4-specific TOMLs)
- Convert 19 team skills from Claude Code format (Agent/SendMessage/TaskCreate)
  to Codex format (spawn_agent/wait_agent/tasks.json/request_user_input)
- Update team-lifecycle-v4 to use generic agent types (team_worker/team_supervisor)
- Convert all coordinator role files: dispatch.md, monitor.md, role.md
- Convert all worker role files: remove run_in_background, fix Bash syntax
- Convert all specs/pipelines.md references
- Final state: 20 team skills, 217 .md files, zero Claude Code API residuals

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-24 16:54:48 +08:00

3.1 KiB

Raw Blame History

IterDev Pipeline Definitions

Three-Pipeline Architecture

Patch Pipeline (2 beats, serial)

DEV-001 -> VERIFY-001
[developer]  [tester]

Sprint Pipeline (4 beats, with parallel window)

DESIGN-001 -> DEV-001 -> [VERIFY-001 + REVIEW-001] (parallel)
[architect]   [developer]  [tester]       [reviewer]

Multi-Sprint Pipeline (N beats, iterative)

Sprint 1: DESIGN-001 -> DEV-001 -> DEV-002(incremental) -> VERIFY-001 -> DEV-fix -> REVIEW-001
Sprint 2: DESIGN-002(refined) -> DEV-003 -> VERIFY-002 -> REVIEW-002
...

Generator-Critic Loop (developer <-> reviewer)

DEV -> REVIEW -> (if review.critical_count > 0 || review.score < 7)
              -> DEV-fix -> REVIEW-2 -> (if still issues) -> DEV-fix-2 -> REVIEW-3
              -> (max 3 rounds, then accept with warning)

Pipeline Selection Logic

Signal	Score
Changed files > 10	+3
Changed files 3-10	+2
Structural change	+3
Cross-cutting concern	+2
Simple fix	-2

Score	Pipeline
>= 5	multi-sprint
2-4	sprint
0-1	patch

Task Metadata Registry

Task ID	Role	Pipeline	Dependencies	Description
DESIGN-001	architect	sprint/multi	(none)	Technical design and task breakdown
DEV-001	developer	all	DESIGN-001 (sprint/multi) or (none for patch)	Code implementation
DEV-002	developer	multi	DEV-001	Incremental implementation
DEV-fix	developer	sprint/multi	REVIEW-* (GC loop trigger)	Fix issues from review
VERIFY-001	tester	all	DEV-001 (or last DEV)	Test execution and fix cycles
REVIEW-001	reviewer	sprint/multi	DEV-001 (or last DEV)	Code review and quality scoring

Checkpoints

Trigger Condition	Location	Behavior
GC loop exceeds max rounds	After REVIEW-3	Stop iteration, accept with warning, record in wisdom
Sprint transition	End of Sprint N	Pause, retrospective, user confirms `resume` for Sprint N+1
Pipeline stall	No ready + no running tasks	Check missing tasks, report blockedBy chain to user

Multi-Sprint Dynamic Downgrade

If Sprint N metrics are strong (velocity >= expected, review avg >= 8), coordinator may downgrade Sprint N+1 from multi-sprint to sprint pipeline for efficiency.

Task Ledger Schema

Field	Description
`sprint_id`	Current sprint identifier
`sprint_goal`	Sprint objective
`tasks[]`	Array of task entries
`metrics`	Aggregated metrics: total, completed, in_progress, blocked, velocity

Task Entry Fields:

Field	Description
`id`	Task identifier
`title`	Task title
`owner`	Assigned role
`status`	pending / in_progress / completed / blocked
`started_at` / `completed_at`	Timestamps
`gc_rounds`	Generator-Critic iteration count
`review_score`	Reviewer score (null until reviewed)
`test_pass_rate`	Tester pass rate (null until tested)

3.1 KiB Raw Blame History