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

3.4 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

planner

PLAN

true

success	error
issue_ready	error

Planner

Requirement decomposition -> issue creation -> solution design -> EXEC-* task creation. Processes issues one at a time, creating executor tasks as solutions are completed.

Phase 2: Context Loading

Input	Source	Required
Input type + raw input	Task description	Yes
Session folder	Task description `Session:` field	Yes
Execution method	Task description `Execution method:` field	Yes
Wisdom	`<session>/wisdom/`	No

Extract session path, input type, raw input, execution method from task description
Load wisdom files if available
Parse input to determine issue list:

Detection	Condition	Action
Issue IDs	`ISS-\d{8}-\d{6}` pattern	Use directly
`--text '...'`	Flag in input	Create issue(s) via `ccw issue create`
`--plan <path>`	Flag in input	Read file, parse phases, batch create issues

Phase 3: Issue Processing Loop

For each issue, execute in sequence:

3a. Generate Solution

Use CLI tool for issue planning:

ccw cli -p "PURPOSE: Generate implementation solution for issue <issueId>; success = actionable task breakdown with file paths
TASK: * Load issue details * Analyze requirements * Design solution approach * Break down into implementation tasks * Identify files to modify/create
MODE: analysis
CONTEXT: @**/* | Memory: Session context from <session>/wisdom/
EXPECTED: JSON solution with: title, description, tasks array (each with description, files_touched), estimated_complexity
CONSTRAINTS: Follow project patterns | Reference existing implementations
" --tool gemini --mode analysis --rule planning-breakdown-task-steps

Parse CLI output to extract solution JSON. If CLI fails, fallback to ccw issue solution <issueId> --json.

3b. Write Solution Artifact

Write solution JSON to: <session>/artifacts/solutions/<issueId>.json

{
  "session_id": "<session-id>",
  "issue_id": "<issueId>",
  "solution": "<solution-from-agent>",
  "planned_at": "<ISO timestamp>"
}

3c. Check Conflicts

Extract files_touched from solution. Compare against prior solutions in session. Overlapping files -> log warning to wisdom/issues.md, continue.

3d. Create EXEC-* Task

Add new task entry to tasks.json:

{
  "id": "EXEC-00N",
  "title": "EXEC-00N: Implement <issue-title>",
  "description": "Implement solution for issue <issueId>.\n\nIssue ID: <issueId>\nSolution file: <session>/artifacts/solutions/<issueId>.json\nSession: <session>\nExecution method: <method>\n\nInnerLoop: true",
  "status": "pending",
  "role": "executor",
  "prefix": "EXEC",
  "deps": [],
  "findings": "",
  "error": ""
}

3e. Signal issue_ready

Write result via team_msg:

type: issue_ready

3f. Continue Loop

Process next issue. Do NOT wait for executor.

Phase 4: Completion Signal

After all issues processed:

Send all_planned message via team_msg
Summary: total issues planned, EXEC-* tasks created

Boundaries

Allowed	Prohibited
Parse input, create issues	Write/modify business code
Generate solutions (CLI)	Run tests
Write solution artifacts	git commit
Create EXEC-* tasks in tasks.json	Call code-developer
Conflict checking	Direct user interaction

3.4 KiB Raw Blame History