execute

Automated lifecycle execution dispatches per-task implementer agents, tracks progress via state files, and enforces per-task verification to ensure a traceable workflow from scope to completion.

Orchestrating plan execution involves dispatching task-implementer agents for each plan task, enforcing per-phase checkpoints, and logging artifacts to maintain auditability throughout the software lifecycle.

Yes, you can integrate optional Git commits into the workflow to automatically preserve changes when per-task verification passes, ensuring traceable progress from design to implementation.

Per-task verification works by dispatching implementer agents for individual tasks and enforcing checkpoints after each one, ensuring evidence and implementation traceability before moving to the next phase.

Yes, automated execution follows a structured lifecycle beginning with scope, then research, design, plan, and optional spike phases, ensuring the design evolves properly before final execution begins.

Automated orchestration requires a structured lifecycle progression through scope, research, design, and plan phases beforehand, and relies on state tracking files like state.yml and PROGRESS.md for auditability.