workflow-execute

Autonomous workflow execution discovers active sessions, generates TodoWrite plans, and orchestrates agents task-by-task until completion. It coordinates sequential, parallel, or phased implementation plans by loading per-task JSON files and respecting dependencies automatically.

Autonomous workflow orchestration requires validated IMPL_PLAN.md and TODO_LIST.md files in your project. Tasks must be represented by per-task JSON files, which the orchestrator lazy loads only when each specific task is about to run.

Yes, workflow execution supports the --resume-session flag to skip session discovery and planning. Without this flag, it automatically detects active workflow sessions and prompts you when multiple active sessions exist.

TodoWrite status synchronization generates and advances progress across the entire workflow. One agent instance executes exactly one task JSON, updates the task state, generates a summary, and optionally commits changes after each task completes.

Continuous workflow execution runs without interruption by invoking the command with the --yes flag. This enables autonomous end-to-end processing of sequential, parallel, or phased implementation plans while respecting task dependencies.

Yes, workflow orchestration applies to sequential, parallel, or phased implementation plans. It respects dependencies defined within per-task JSON files, ensuring autonomous agents execute tasks in the correct order across complex schedules.