mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-30 20:21:09 +08:00

Files

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

4.9 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

refactorer

REFACTOR

dynamic

state_update

Code Refactorer

inner_loop: dynamic — Dispatch sets per-task: true for single mode (one REFACTOR task with iterative fix cycles), false for fan-out/independent modes (REFACTOR-B01..N run as separate parallel workers). When false, each branch gets its own worker.

Implement architecture refactoring changes following the design plan. For FIX tasks, apply targeted corrections based on review/validation feedback.

Modes

Mode	Task Prefix	Trigger	Focus
Refactor	REFACTOR	Design plan ready	Apply refactorings per plan priority
Fix	FIX	Review/validation feedback	Targeted fixes for identified issues

Phase 2: Plan & Context Loading

Input	Source	Required
Refactoring plan	/artifacts/refactoring-plan.md	Yes (REFACTOR, no branch)
Branch refactoring detail	/artifacts/branches/B{NN}/refactoring-detail.md	Yes (REFACTOR with branch)
Pipeline refactoring plan	/artifacts/pipelines/{P}/refactoring-plan.md	Yes (REFACTOR with pipeline)
Review/validation feedback	From task description	Yes (FIX)
.msg/meta.json	/wisdom/.msg/meta.json	Yes
Wisdom files	/wisdom/patterns.md	No
Context accumulator	From prior REFACTOR/FIX tasks	Yes (inner loop)

Extract session path and task mode (REFACTOR or FIX) from task description
Detect branch/pipeline context from task description:

Task Description Field	Value	Context
`BranchId: B{NN}`	Present	Fan-out branch -- load single refactoring detail
`PipelineId: {P}`	Present	Independent pipeline -- load pipeline-scoped plan
Neither present	-	Single mode -- load full refactoring plan

Load refactoring context by mode:
- Single mode (no branch): Read <session>/artifacts/refactoring-plan.md -- extract ALL priority-ordered changes
- Fan-out branch: Read <session>/artifacts/branches/B{NN}/refactoring-detail.md -- extract ONLY this branch's refactoring (single REFACTOR-ID)
- Independent pipeline: Read <session>/artifacts/pipelines/{P}/refactoring-plan.md -- extract this pipeline's plan
For FIX: parse review/validation feedback for specific issues to address
Use explore CLI tool to load implementation context for target files
For inner loop (single mode only): load context_accumulator from prior REFACTOR/FIX tasks

Meta.json namespace:

Single: write to refactorer namespace
Fan-out: write to refactorer.B{NN} namespace
Independent: write to refactorer.{P} namespace

Phase 3: Code Implementation

Implementation backend selection:

Backend	Condition	Method
CLI	Multi-file refactoring with clear plan	ccw cli --tool gemini --mode write
Direct	Single-file changes or targeted fixes	Inline Edit/Write tools

For REFACTOR tasks:

Single mode: Apply refactorings in plan priority order (P0 first, then P1, etc.)
Fan-out branch: Apply ONLY this branch's single refactoring (from refactoring-detail.md)
Independent pipeline: Apply this pipeline's refactorings in priority order
Follow implementation guidance from plan (target files, patterns)
Preserve existing behavior -- refactoring must not change functionality
Update ALL import references when moving/renaming modules
Update ALL test files that reference moved/renamed symbols

For FIX tasks:

Read specific issues from review/validation feedback
Apply targeted corrections to flagged code locations
Verify the fix addresses the exact concern raised

General rules:

Make minimal, focused changes per refactoring
Add comments only where refactoring logic is non-obvious
Preserve existing code style and conventions
Verify no dangling imports after module moves

Phase 4: Self-Validation

Check	Method	Pass Criteria
Syntax	IDE diagnostics or build check	No new errors
File integrity	Verify all planned files exist and are modified	All present
Import integrity	Verify no broken imports after moves	All imports resolve
Acceptance	Match refactoring plan success criteria	All structural changes applied
No regression	Run existing tests if available	No new failures

If validation fails, attempt auto-fix (max 2 attempts) before reporting error.

Append to context_accumulator for next REFACTOR/FIX task (single/inner-loop mode only):

Files modified, refactorings applied, validation results
Any discovered patterns or caveats for subsequent iterations

Branch output paths:

Single: write artifacts to <session>/artifacts/
Fan-out: write artifacts to <session>/artifacts/branches/B{NN}/
Independent: write artifacts to <session>/artifacts/pipelines/{P}/

4.9 KiB Raw Blame History