harness-execute

To execute a plan with an audit trail, load the active plan from docs/exec-plans/active/, update task checkboxes sequentially, and capture evidence for each completed step to maintain a verifiable record.

Plan-driven task execution processes sequential steps from an active plan while identifying and logging blockers. It updates task statuses and captures evidence to ensure controlled, verifiable software delivery.

You record verification evidence during plan execution by following the active plan steps in order and documenting evidence directly as each task completes, ensuring all verification handoffs are explicitly satisfied.

Yes, plan execution supports completion handoffs by transferring the verified plan to harness-verify and harness-finish once all sequential tasks are complete and explicit verification steps are satisfied.

Yes, you can use this for plan-driven software delivery tasks in controlled environments. It handles plan loading, per-task checkbox updates, blocker handling, and explicit verification handoffs.

The best way to manage an active plan is to load it from docs/exec-plans/active/, review linked specs, identify blockers, execute tasks sequentially while updating checkboxes, and capture evidence for each step.