single-flow-task-execution

Sequential task execution processes implementation plans one task at a time without parallel subagents, ensuring deterministic single-flow progress and maintaining code clarity through structured task boundaries.

A two-stage review gate checks task spec compliance first, then evaluates code quality, ensuring each completed task meets requirements and standards before advancing to the next sequential task.

Progress tracking updates docs/plans/task.md to reflect state after each task boundary, ensuring the implementation plan stays synchronized with completed work and pending tasks.

Single-task execution applies to plans containing multiple independent tasks, guiding execution in a controlled sequence with per-task scoping and review gates to prevent parallel work.

Avoid sequential execution when tasks require parallelism or lack clear boundaries, as this approach enforces single-thread flow with strict review gates and no parallel coding support.

Review gates validate spec compliance then code quality after each task, ensuring implementation plans meet requirements and standards before proceeding to the next controlled task.