evanflow-executing-plans

To execute a coding plan with inline verification, load your plan file and process tasks sequentially. The workflow enforces per-task status tracking, TDD flow, and project-wide quality checks before marking any task complete.

Yes, you can parallelize plan execution using a coder-overseer workflow when your plan contains three or more independent units that share a common interface contract.

The TDD flow for task-by-task execution involves running inline verifications and built-in quality checks on each unit. Per-task status updates are enforced, and tasks are only marked complete after passing these checks.

When handling blockers during complex plan execution, the workflow uses blocker-aware prompts and stops execution upon encountering a blocker rather than forcing sub-skill chains or skipping the issue.

No specific plan format is required, but the plan must contain multiple tasks or independent units sharing a contract to enable either sequential execution or parallel coder-overseer orchestration.

The best way to track task status during multi-unit plan execution is through enforced per-task status updates. The workflow automatically manages these updates alongside inline verifications before completion.