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

5.2 KiB

Raw Blame History

Pipeline Definitions

1. Pipeline Selection Criteria

Keywords	Pipeline
spec, design, document, requirements	`spec-only`
implement, build, fix, code	`impl-only`
full, lifecycle, end-to-end	`full-lifecycle`
frontend, UI, react, vue	`fe-only` or `fullstack`
Ambiguous / unclear	request_user_input

2. Spec-Only Pipeline

6 tasks + 2 optional checkpoints

RESEARCH-001 -> DRAFT-001 -> DRAFT-002 -> [CHECKPOINT-001] -> DRAFT-003 -> DRAFT-004 -> [CHECKPOINT-002] -> QUALITY-001

Task	Role	Description
RESEARCH-001	analyst	Research domain, competitors, constraints
DRAFT-001	writer	Product brief, self-validate
DRAFT-002	writer	Requirements PRD
CHECKPOINT-001	supervisor	Brief<->PRD consistency, terminology alignment
DRAFT-003	writer	Architecture design, self-validate
DRAFT-004	writer	Epics & stories, self-validate
CHECKPOINT-002	supervisor	Full spec consistency (4 docs), quality trend
QUALITY-001	reviewer	Quality gate scoring

Checkpoint: After QUALITY-001 -- pause for user approval before any implementation.

Supervision opt-out: Set supervision: false in tasks.json to skip CHECKPOINT tasks.

3. Impl-Only Pipeline

4 tasks + 1 optional checkpoint

PLAN-001 -> [CHECKPOINT-003] -> IMPL-001 -> TEST-001 + REVIEW-001

Task	Role	Description
PLAN-001	planner	Break down into implementation steps, assess complexity
CHECKPOINT-003	supervisor	Plan<->input alignment, complexity sanity check
IMPL-001	implementer	Execute implementation plan
TEST-001	tester	Validate against acceptance criteria
REVIEW-001	reviewer	Code review

TEST-001 and REVIEW-001 run in parallel after IMPL-001 completes.

Supervision opt-out: Set supervision: false in tasks.json to skip CHECKPOINT tasks.

4. Full-Lifecycle Pipeline

10 tasks + 3 optional checkpoints = spec-only (6+2) + impl (4+1)

[Spec pipeline with CHECKPOINT-001/002] -> PLAN-001(blockedBy: QUALITY-001) -> [CHECKPOINT-003] -> IMPL-001 -> TEST-001 + REVIEW-001

PLAN-001 is blocked until QUALITY-001 passes and user approves the checkpoint.

Supervision opt-out: Set supervision: false in tasks.json to skip all CHECKPOINT tasks.

5. Frontend Pipelines

Pipeline	Description
`fe-only`	Frontend implementation only: PLAN-001 -> IMPL-001 (fe-implementer) -> TEST-001 + REVIEW-001
`fullstack`	Backend + frontend: PLAN-001 -> IMPL-001 (backend) + IMPL-002 (frontend) -> TEST-001 + REVIEW-001
`full-lifecycle-fe`	Full spec pipeline -> fullstack impl pipeline

6. Conditional Routing

PLAN-001 outputs a complexity assessment that determines the impl topology.

Complexity	Modules	Route
Low	1-2	PLAN-001 -> IMPL-001 -> TEST + REVIEW
Medium	3-4	PLAN-001 -> ORCH-001 -> IMPL-{1..N} (parallel) -> TEST + REVIEW
High	5+	PLAN-001 -> ARCH-001 -> ORCH-001 -> IMPL-{1..N} -> TEST + REVIEW

ORCH-001 (orchestrator): Coordinates parallel IMPL tasks, manages dependencies
ARCH-001 (architect): Detailed architecture decisions before orchestration

7. Task Metadata Registry

Task ID	Role	Phase	Depends On	Priority
RESEARCH-001	analyst	research	-	P0
DRAFT-001	writer	product-brief	RESEARCH-001	P0
DRAFT-002	writer	requirements	DRAFT-001	P0
DRAFT-003	writer	architecture	DRAFT-002	P0
DRAFT-004	writer	epics	DRAFT-003	P0
QUALITY-001	reviewer	readiness	CHECKPOINT-002 (or DRAFT-004)	P0
CHECKPOINT-001	supervisor	checkpoint	DRAFT-002	P1
CHECKPOINT-002	supervisor	checkpoint	DRAFT-004	P1
CHECKPOINT-003	supervisor	checkpoint	PLAN-001	P1
PLAN-001	planner	planning	QUALITY-001 (or user input)	P0
ARCH-001	architect	arch-detail	PLAN-001	P1
ORCH-001	orchestrator	orchestration	PLAN-001 or ARCH-001	P1
IMPL-001	implementer	implementation	PLAN-001 or ORCH-001	P0
IMPL-{N}	implementer	implementation	ORCH-001	P0
TEST-001	tester	validation	IMPL-*	P0
REVIEW-001	reviewer	review	IMPL-*	P0

8. Dynamic Specialist Injection

When task content or user request matches trigger keywords, inject a specialist task.

Trigger Keywords	Specialist Role	Task Prefix	Priority	Insert After
security, vulnerability, OWASP	security-expert	SECURITY-*	P0	PLAN
performance, optimization, latency	performance-optimizer	PERF-*	P1	IMPL
data, pipeline, ETL, migration	data-engineer	DATA-*	P0	parallel with IMPL
devops, CI/CD, deployment, infra	devops-engineer	DEVOPS-*	P1	IMPL
ML, model, training, inference	ml-engineer	ML-*	P0	parallel with IMPL

Injection rules:

Specialist tasks inherit the session context and wisdom
They write discoveries/{task_id}.json on completion like any other task
P0 specialists block downstream tasks; P1 run in parallel

5.2 KiB Raw Blame History