executing-phase-tasks

Execute phase tasks

When cc already has a ready phase task list and execution is about to begin, use this phase.

Roles

• cc: select the next executable phase, dispatch a worker, track progress and blockers
• worker: execute one phase task list in order, and append results after each task

Rules

• Only execute one active dependency phase at a time
• Do not skip tasks unless the task list explicitly allows it
• After completing each task, append a phase result
• If verification fails, or the task list does not match repository reality, stop and report

Process

1. Select the next executable phase:
   • task list is ready
   • dependencies are satisfied
   • required prerequisite phase review has passed
2. Dispatch a worker to execute that phase task list
3. Require the worker to process tasks in order
4. After each task, append to the phase result document:
   • task id
   • status
   • summary of work done
   • changed files or artifacts
   • verification run
   • follow-up notes
5. If a task is blocked:
   • record the blocker in the phase result document
   • immediately notify cc
   • stop, do not guess
6. After the last task is complete, mark phase execution complete, and enter reviewing-phase-results

Execution discipline

• Do only one task at a time
• Every task must have explicit verification
• Result history is append-only
• Do not secretly change the plan during execution

Exit conditions

There are only two ways to leave:

• The current phase task list has been fully executed
• Execution is blocked and requires cc intervention

Anti-patterns

• Packing multiple tasks into one unchecked large change
• Losing task-by-task execution history
• Claiming completion before the phase result has been fully updated