orchestrator

Automating end-to-end plan execution involves ingesting task-based or spec-driven planning outputs, then dispatching them through deterministic, gated phases using worktree-isolated execution, build/test gates, and a phase finisher for cleanup.

Worktree isolation in phased workflow orchestration separates execution environments for each task, ensuring that batch or team mode operations run independently before a phase finisher handles merge and cleanup operations.

You can resume an interrupted Claude Code workflow phase because the orchestrator enforces deterministic phase progression and supports resumption, using handoff.md and progress-log.md for audit, tracking, and recovery.

Yes, automated workflow orchestration applies to both spec-driven and task-based planning, ingesting the plan directory outputs and selecting and assigning skills to each phase of execution.

The best way to track progress and handoffs in automated plan execution is by monitoring the handoff.md and progress-log.md files, which provide comprehensive post-phase reporting for audit and recovery.

Build and test gates are required for phased workflow automation to ensure deterministic progression, verifying task completion within worktree-isolated execution before a phase finisher handles merge and cleanup.