Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v3/roles/pipeline/executor.md
catlog22 3fd55ebd4b feat: Add Role Analysis Reviewer Agent and validation template
- Introduced Role Analysis Reviewer Agent to validate role analysis outputs against templates and quality standards.
- Created a detailed validation ruleset for the system-architect role, including mandatory and recommended sections.
- Added JSON validation report structure for output.
- Implemented execution command for validation process.

test: Add UX tests for HookCard component

- Created comprehensive tests for HookCard component, focusing on delete confirmation UX pattern.
- Verified confirmation dialog appearance, deletion functionality, and button interactions.
- Ensured proper handling of state updates and visual feedback for enabled/disabled status.

test: Add UX tests for ThemeSelector component

- Developed tests for ThemeSelector component, emphasizing delete confirmation UX pattern.
- Validated confirmation dialog display, deletion actions, and toast notifications for undo functionality.
- Ensured proper management of theme slots and state updates.

feat: Implement useDebounce hook

- Added useDebounce hook to delay expensive computations or API calls, enhancing performance.

feat: Create System Architect Analysis Template

- Developed a comprehensive template for system architect role analysis, covering required sections such as architecture overview, data model, state machine, error handling strategy, observability requirements, configuration model, and boundary scenarios.
- Included examples and templates for each section to guide users in producing SPEC.md-level precision modeling.
2026-03-05 19:58:10 +08:00

2.1 KiB

role, prefix, inner_loop, discuss_rounds, input_artifact_types, message_types
role prefix inner_loop discuss_rounds input_artifact_types 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