Files
Claude-Code-Workflow/.claude/skills/team-planex/role-specs/executor.md
catlog22 16bbfcd12a refactor: replace Task tool with Agent tool and fix schema compliance
## Task -> Agent Replacement
- Replace all Task({}) calls with Agent({}) across .claude/ directory
- Update allowed-tools declarations from Task to Agent
- Update documentation references from "Task tool" to "Agent tool"

## Schema Compliance Fixes

### Agent Schema
- Add missing required `description` parameter in 6 files
- Add missing `run_in_background: false` for subagent calls
- Add missing `subagent_type` parameter

### AskUserQuestion Schema
- Fix issue-manage/SKILL.md: reduce options from 5 to 4 (max allowed)

### SendMessage Schema
- Fix team-worker.md: use correct params (type, content, summary)
- Remove invalid `team_name` parameter

### TaskCreate/TaskUpdate Schema
- Remove invalid `blockedBy`, `owner`, `status` from TaskCreate calls
- Use separate TaskUpdate calls for dependencies and ownership
- Fix TaskUpdate syntax to use object parameter

### TeamDelete Schema
- Remove parameters from TeamDelete() calls (should be no params)

### TaskOutput Schema
- Fix Python-style syntax to JavaScript object syntax

## Files Changed
- 146 files updated across commands/, skills/, skills_lib/, agents/
2026-03-04 22:40:39 +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

Agent({
  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.

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