Files
Claude-Code-Workflow/.codex/skills/team-roadmap-dev/roles/executor/role.md
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.4 KiB

role, prefix, inner_loop, cli_tools, message_types
role prefix inner_loop cli_tools message_types
executor EXEC true
gemini --mode write
success progress error
exec_complete exec_progress error

Executor

Wave-based code implementation per phase. Reads IMPL-*.json task files, computes execution waves from the dependency graph, delegates each task to CLI tool for code generation. Produces summary-{IMPL-ID}.md per task.

Phase 2: Context Loading

Input Source Required
Task JSONs /phase-{N}/.task/IMPL-*.json Yes
Prior summaries /phase-{1..N-1}/summary-*.md No
Wisdom /wisdom/ No
  1. Glob <session>/phase-{N}/.task/IMPL-*.json, error if none found
  2. Parse each task JSON: extract id, description, depends_on, files, convergence, implementation
  3. Compute execution waves from dependency graph:
    • Wave 1: tasks with no dependencies
    • Wave N: tasks whose all deps are in waves 1..N-1
    • Force-assign if circular (break at lowest-numbered task)
  4. Load prior phase summaries for cross-task context

Phase 3: Wave-Based Implementation

Execute waves sequentially, tasks within each wave can be parallel.

Strategy selection:

Task Count Strategy
<= 2 Direct: inline Edit/Write
3-5 Single CLI tool call for all
> 5 Batch: one CLI tool call per module group

Per task:

  1. Build prompt from task JSON: description, files, implementation steps, convergence criteria
  2. Include prior summaries and wisdom as context
  3. Delegate to CLI tool:
    Bash({
      command: `ccw cli -p "PURPOSE: Implement task ${taskId}: ${description}
    TASK: ${implementationSteps}
    MODE: write
    CONTEXT: @${files.join(' @')} | Memory: ${priorSummaries}
    EXPECTED: Working code changes matching convergence criteria
    CONSTRAINTS: ${convergenceCriteria}" --tool gemini --mode write`
    })
    
  4. Write <session>/phase-{N}/summary-{IMPL-ID}.md with: task ID, affected files, changes made, status

Between waves: report wave progress via team_msg (type: exec_progress)

Phase 4: Self-Validation

Check Method Pass Criteria
Affected files exist test -f <path> for each file in summary All present
TypeScript syntax npx tsc --noEmit (if tsconfig.json exists) No errors
Lint npm run lint (best-effort) No critical errors

Log errors via team_msg but do NOT fix — verifier handles gap detection.