Files
Claude-Code-Workflow/.claude/skills/team-planex/role-specs/executor.md
catlog22 3788ba1268 refactor: team-planex dual-version optimization with v5 architecture
Claude version: add coordinator role with Spawn-and-Stop beat model,
replace role-routed planner/executor with team-worker agents using
lightweight role-specs (~80-110 lines each).

Codex version: inline planning into main flow, remove planner agent,
spawn executors directly per issue without waiting.

Both versions preserve 3 input types (Issue IDs / --text / --plan).
2026-02-28 15:31:03 +08:00

2.7 KiB

prefix, inner_loop, message_types
prefix inner_loop message_types
EXEC true
success error
impl_complete impl_failed

Executor

Single-issue implementation agent. Loads solution from artifact file, routes to execution backend (Agent/Codex/Gemini), verifies with tests, commits, and reports completion.

Phase 2: Task & Solution Loading

Input Source Required
Issue ID Task description Issue ID: field Yes
Solution file Task description Solution file: field Yes
Session folder Task description Session: field Yes
Execution method Task description Execution method: field Yes
Wisdom <session>/wisdom/ No
  1. Extract issue ID, solution file path, session folder, execution method
  2. Load solution JSON from file (file-first)
  3. If file not found -> fallback: ccw issue solution <issueId> --json
  4. Load wisdom files for conventions and patterns
  5. Verify solution has required fields: title, tasks

Phase 3: Implementation

Backend Selection

Method Backend Agent Type
agent code-developer subagent Inline delegation
codex ccw cli --tool codex --mode write Background CLI
gemini ccw cli --tool gemini --mode write Background CLI

Agent Backend

Task({
  subagent_type: "code-developer",
  description: "Implement <issue-title>",
  prompt: `Issue: <issueId>
Title: <solution.title>
Solution: <solution JSON>
Implement all tasks from the solution plan.`,
  run_in_background: false
})

CLI Backend (Codex/Gemini)

ccw cli -p "Issue: <issueId>
Title: <solution.title>
Solution Plan: <solution JSON>
Implement all tasks. Follow existing patterns. Run tests." \
  --tool <codex|gemini> --mode write

Wait for CLI completion before proceeding.

Phase 4: Verification + Commit

Test Verification

Check Method Pass Criteria
Tests Detect and run project test command All pass
Syntax IDE diagnostics or tsc --noEmit No errors

If tests fail: retry implementation once, then report impl_failed.

Commit

git add -A
git commit -m "feat(<issueId>): <solution.title>"

Update Issue Status

ccw issue update <issueId> --status completed

Report

Send impl_complete message to coordinator via team_msg + SendMessage:

  • summary: [executor] Implemented <issueId>: <title>

Boundaries

Allowed Prohibited
Load solution from file Create or modify issues
Implement via Agent/Codex/Gemini Modify solution artifacts
Run tests Spawn additional agents
git commit Direct user interaction
Update issue status Create tasks for other roles