Files
Claude-Code-Workflow/.claude/skills/team-lifecycle/role-specs/executor.md
catlog22 fd847070d5 Refactor architecture optimization and issue resolution workflows
- Enhanced multi-perspective discussion capabilities in discuss-subagent for architecture optimization, integrating CLI tools for structured analysis and recommendations.
- Updated explore-subagent to utilize CLI tools directly for architecture-critical structure exploration, improving efficiency.
- Streamlined discuss-subagent in team-coordinate to leverage CLI for multi-perspective critiques, enhancing artifact evaluation.
- Modified explore-subagent in team-coordinate to adopt CLI tools for codebase exploration, ensuring consistency across roles.
- Expanded team-issue skill to include additional tools for issue resolution, refining role-specific execution and restrictions.
- Improved explorer role specifications to utilize CLI for exploration tasks, enhancing context gathering for architecture-critical structures.
- Adjusted implementer role specifications to route execution through CLI tools, optimizing backend selection for task execution.
- Enhanced integrator role specifications to utilize CLI for queue formation, improving issue resolution efficiency.
- Updated planner role specifications to leverage CLI for solution generation, ensuring structured implementation planning.
- Refined analyst role specifications to utilize CLI for codebase exploration, enhancing context generation for research.
- Adjusted executor role specifications to utilize CLI tools for task execution, improving backend selection and error handling.
- Enhanced writer role specifications to generate documents using CLI tools, streamlining document generation processes.
- Updated team-planex skill to reflect changes in execution methods, focusing on CLI tools for task execution.
- Refined team-testing role specifications to utilize CLI for test generation and failure resolution, improving testing workflows.
- Enhanced ultra-analyze role specifications to leverage CLI tools for discussion and exploration tasks, improving analysis depth and clarity.
2026-03-04 23:19:36 +08:00

2.1 KiB

role, prefix, inner_loop, discuss_rounds, subagents, message_types
role prefix inner_loop discuss_rounds subagents message_types
executor IMPL true
success progress error
impl_complete impl_progress error

Executor — Phase 2-4

Phase 2: Task & Plan Loading

Objective: Load plan and determine execution strategy.

  1. Load plan.json and .task/TASK-*.json from <session-folder>/plan/

Backend selection (priority order):

Priority Source Method
1 Task metadata task.metadata.executor field
2 Plan default "Execution Backend:" in plan
3 Auto-select Simple (< 200 chars, no refactor) → agent; Complex → codex

Code review selection:

Priority Source Method
1 Task metadata task.metadata.code_review field
2 Plan default "Code Review:" in plan
3 Auto-select Critical keywords (auth, security, payment) → enabled

Phase 3: Code Implementation

Objective: Execute implementation across batches.

Batching: Topological sort by IMPL task dependencies → sequential batches.

Backend Invocation Use Case
gemini ccw cli --tool gemini --mode write (foreground) Simple, direct edits
codex ccw cli --tool codex --mode write (foreground) Complex, architecture
qwen ccw cli --tool qwen --mode write (foreground) Alternative backend

Phase 4: Self-Validation

Step Method Pass Criteria
Syntax check tsc --noEmit (30s) Exit code 0
Acceptance criteria Match criteria keywords vs implementation All addressed
Test detection Find .test.ts/.spec.ts for modified files Tests identified
Code review (optional) gemini analysis or codex review No blocking issues

Report: task ID, status, files modified, validation results, backend used.

Error Handling

Scenario Resolution
Syntax errors Retry with error context (max 3)
Missing dependencies Request from coordinator
Backend unavailable Fallback to alternative tool
Circular dependencies Abort, report graph