verification-sweep

Verification Sweep

Algorithm for verifying task completion by running verification commands and updating plan status.

Purpose

Verification sweep establishes ground truth about task completion:

• Run verification commands to prove tasks are done
• Update plan file with accurate statuses
• Detect regressions in previously complete tasks
• Report what work remains

When to Use

Perform verification sweep:

• At the start of /tommymorgan:work (before doing any work)
• When running /tommymorgan:status
• After returning from a break or new session
• Before reporting completion status

Algorithm

Step 1: Load Plan File

Read the plan file and extract all tasks:

For each line matching "### \d+\. ":
  - task_number = extracted number
  - task_description = text after number
  - verify_command = content of next **Verify**: `...`
  - current_status = value after **Status**:

Step 2: Run Verification Commands

For each task, execute its verification command:

<verify_command>
echo "Exit code: $?"

Capture:

• Exit code (0 = success)
• Stdout/stderr (for debugging)

Step 3: Determine New Status

Apply status transition rules:

Current Status	Exit Code	New Status	Action
pending	0	complete	Update plan
pending	non-zero	pending	No change
complete	0	complete	No change
complete	non-zero	complete	Warn: regression
blocked	0	complete	Update plan, clear block
blocked	non-zero	blocked	No change

Regression handling: If a previously complete task now fails, warn but do not change status:

WARNING: Regression detected in task N: <description>
Verification command failed but task marked complete.
Investigate before continuing.

Step 4: Update Plan File

For each status change, update the plan file:

Find:

**Status**: pending

Replace with:

**Status**: complete

Use precise edits - only change the status value, preserve everything else.