manual_slop/.opencode/commands/conductor-verify.md

description, agent

description	agent
Verify phase completion and create checkpoint commit	tier2-tech-lead

/conductor-verify

Execute phase completion verification and create checkpoint.

Prerequisites

• All tasks in the current phase must be marked [x]
• All changes must be committed

Verification Protocol

1. Announce Protocol Start: Inform user that phase verification has begun.

2. Determine Phase Scope:

   • Find previous phase checkpoint SHA in plan.md
   • If no previous checkpoint, scope is all changes since first commit

3. List Changed Files:

   git diff --name-only <previous_checkpoint_sha> HEAD
   

4. Verify Test Coverage: For each code file changed (exclude .json, .md, .yaml):

   • Check if corresponding test file exists
   • If missing, create test file via @tier3-worker

5. Execute Tests in Batches: CRITICAL: Do NOT run full suite. Run max 4 test files at a time.

   Announce command before execution:

   I will now run: uv run pytest tests/test_file1.py tests/test_file2.py -v
   

   If tests fail with large output:

   • Pipe to log file
   • Delegate analysis to @tier4-qa
   • Maximum 2 fix attempts before escalating

6. Present Results:

   ## Phase Verification Results
   
   **Phase:** {phase name}
   **Files Changed:** {count}
   **Tests Run:** {count}
   **Tests Passed:** {count}
   **Tests Failed:** {count}
   
   [Detailed results or failure analysis]
   

7. Await User Confirmation: PAUSE and wait for explicit user approval before proceeding.

8. Create Checkpoint:

   git add .
   git commit --allow-empty -m "conductor(checkpoint): Phase {N} complete"
   $hash = git log -1 --format="%H"
   git notes add -m "Verification: [report summary]" $hash
   

9. Update Plan:

   • Add [checkpoint: {sha}] to phase heading in plan.md
   • Commit: git add plan.md && git commit -m "conductor(plan): Mark phase complete"

10. Announce Completion: Inform user that phase is complete with checkpoint created.

Error Handling

• If any verification fails: HALT and present logs
• Do NOT proceed without user confirmation
• Maximum 2 fix attempts per failure