Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v2/role-specs/executor.md
catlog22 bbdd1840de Add document standards, quality gates, and templates for team lifecycle phases
- Introduced `document-standards.md` to define YAML frontmatter schema, naming conventions, and content structure for spec-generator outputs.
- Created `quality-gates.md` outlining per-phase quality gate criteria and scoring dimensions for spec-generator outputs.
- Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to streamline documentation in respective phases.
2026-03-04 23:54:20 +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