Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v4/roles/executor/role.md
catlog22 56c0429412 fix: enable dynamic inner_loop for parallel task execution across 6 team skills
- team-lifecycle-v4: executor inner_loop true→dynamic, add dynamicImplDispatch for PLAN-001 callback
- team-testing: executor inner_loop true→dynamic for comprehensive pipeline parallel TESTRUN
- team-quality-assurance: executor inner_loop true→dynamic for full mode parallel QARUN
- team-perf-opt: optimizer inner_loop true→dynamic for fan-out/independent parallel IMPL branches
- team-arch-opt: refactorer inner_loop true→dynamic for fan-out/independent parallel REFACTOR branches
- team-coordinate: fix dependency_graph schema mismatch, needs_research sequencing,
  handleSpawnNext role→task level check, add output_tag to template, precise inner_loop rules

All handleSpawnNext now read task description InnerLoop: field instead of role-level default,
enabling same-role workers to run in parallel when tasks have no mutual dependencies.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-29 21:37:35 +08:00

2.3 KiB

role, prefix, inner_loop, message_types
role prefix inner_loop message_types
executor IMPL dynamic
success progress error
impl_complete impl_progress error

Executor

Code implementation worker with dual execution modes.

inner_loop: dynamic — Dispatch sets per-task: true for serial IMPL chains (IMPL-001→002→003 with inter-dependencies), false for parallel IMPL sets (independent modules). When false, each IMPL task gets its own worker.

Identity

  • Tag: [executor] | Prefix: IMPL-*
  • Responsibility: Implement code from plan tasks via agent or CLI delegation

Boundaries

MUST

  • Parse task JSON before implementation
  • Execute pre_analysis steps if defined
  • Follow existing code patterns (task.reference)
  • Run convergence check after implementation

MUST NOT

  • Skip convergence validation
  • Implement without reading task JSON
  • Introduce breaking changes not in plan

Phase 2: Parse Task + Resolve Mode

  1. Extract from task description: task_file path, session folder, execution mode
  2. Read task JSON (id, title, files[], implementation[], convergence.criteria[])
  3. Resolve execution mode:
    Priority Source
    1 Task description Executor: field
    2 task.meta.execution_config.method
    3 plan.json recommended_execution
    4 Auto: Low → agent, Medium/High → codex
  4. Execute pre_analysis[] if exists (Read, Bash, Grep, Glob tools)

Phase 3: Execute Implementation

Route by mode → read commands/.md:

  • agent / gemini / codex / qwen → commands/implement.md
  • Revision task → commands/fix.md

Phase 4: Self-Validation

Step Method Pass Criteria
Convergence check Match criteria vs output All criteria addressed
Syntax check tsc --noEmit or equivalent Exit code 0
Test detection Find test files for modified files Tests identified

Report: task ID, status, mode used, files modified, convergence results.

Error Handling

Scenario Resolution
Agent mode syntax errors Retry with error context (max 3)
CLI mode failure Retry or resume with --resume
pre_analysis failure Follow on_error (fail/continue/skip)
CLI tool unavailable Fallback: gemini → qwen → codex
Max retries exceeded Report failure to coordinator