mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-26 19:56:37 +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

2.9 KiB

Raw Blame History

Pipeline Definitions — Team Coordinate

Dynamic Pipeline Model

team-coordinate does NOT have a static pipeline. All pipelines are generated at runtime from task-analysis.json based on the user's task description.

Pipeline Generation Process

Phase 1: analyze-task.md
  -> Signal detection -> capability mapping -> dependency graph
  -> Output: task-analysis.json

Phase 2: dispatch.md
  -> Read task-analysis.json dependency graph
  -> Create tasks.json entries per dependency node
  -> Set deps chains from graph edges
  -> Output: tasks.json with correct DAG

Phase 3-N: monitor.md
  -> handleSpawnNext: spawn ready tasks as team-worker agents
  -> handleCallback: mark completed, advance pipeline
  -> Repeat until all tasks done

Dynamic Task Naming

Capability	Prefix	Example
researcher	RESEARCH	RESEARCH-001
developer	IMPL	IMPL-001
analyst	ANALYSIS	ANALYSIS-001
designer	DESIGN	DESIGN-001
tester	TEST	TEST-001
writer	DRAFT	DRAFT-001
planner	PLAN	PLAN-001
(default)	TASK	TASK-001

Dependency Graph Structure

task-analysis.json encodes the pipeline:

{
  "dependency_graph": {
    "RESEARCH-001": { "role": "researcher", "blockedBy": [], "priority": "P0" },
    "IMPL-001":     { "role": "developer",  "blockedBy": ["RESEARCH-001"], "priority": "P1" },
    "TEST-001":     { "role": "tester",     "blockedBy": ["IMPL-001"], "priority": "P2" }
  }
}

Role-Worker Map

Dynamic — loaded from session role-specs at runtime:

<session>/role-specs/<role-name>.md -> team-worker agent

Role-spec files contain YAML frontmatter:

---
role: <role-name>
prefix: <PREFIX>
inner_loop: <true|false>
message_types:
  success: <type>
  error: error
---

Checkpoint

Trigger	Behavior
capability_gap reported	handleAdapt: generate new role-spec, spawn new worker
consensus_blocked HIGH	Create REVISION task or pause for user
All tasks complete	handleComplete: interactive completion action

Specs Reference

role-spec-template.md — Template for generating dynamic role-specs
quality-gates.md — Quality thresholds and scoring dimensions
knowledge-transfer.md — Context transfer protocols between roles

Quality Gate Integration

Dynamic pipelines reference quality thresholds from specs/quality-gates.md.

Gate Point	Trigger	Criteria Source
After artifact production	Producer role Phase 4	Behavioral Traits in role-spec
After validation tasks	Tester/analyst completion	quality-gates.md thresholds
Pipeline completion	All tasks done	Aggregate scoring

Issue classification: Error (blocks) > Warning (proceed with justification) > Info (log for future).

2.9 KiB Raw Blame History