Verify Checklist

Check in order:

1. Shared rules — look for <verification-checklist> in instruction files (always loaded)
2. Tool extensions — <completion-gate> and <delivery> for tool-specific implementation
3. Project config — project-level overrides or additions (AGENTS.md, CLAUDE.md, etc.)
4. Memory files — any supplemental verification workflows

If no verification workflows found anywhere:

STOP. Tell the user:

"No verification workflows found in memory or instruction files. I recommend adding verification workflow memories at the user and/or project level so future work can be audited. Would you like help creating these?"

Then proceed with best-effort verification using whatever project conventions you can infer. Do not silently skip.

2. Audit

For each verification workflow step:

1. Check: Did you complete this step during this session? What evidence exists?
2. If completed: Record the result (test output, review findings, commit SHAs)
3. If NOT completed: Execute it now. Do not merely report it missing — do the work, then record the result.
4. If blocked: Record why and flag for the user

Do not skip steps. Do not reorder steps. Do not decide steps "don't apply."

3. Gather Context

Collect before writing the report:

• Task objective — What were you asked to do? One sentence.
• PRs — Branch names, PR URLs/numbers, current status
• Remaining work — Anything incomplete if this was a partial delivery
• Discovered work — Issues found but not addressed during implementation
• Where recorded — Bead IDs, issue numbers, memory entries for each discovered item

If discovered work is unrecorded, record it now (create beads, issues, or memory entries as appropriate for the project). Unrecorded work is lost work.

4. Produce the Report

## Completion Report

### Objective
[One-sentence description of the task]

### Pull Requests
| PR | Branch | Status |
|----|--------|--------|
| #N or URL | branch-name | open / merged / draft |

### Verification Checklist
| # | Step | Status | Notes |
|---|------|--------|-------|
| 1 | [step from workflows] | done | [evidence or result] |
| 2 | [step from workflows] | just completed | [what was done now] |
| 3 | [step from workflows] | blocked | [why] |
| 4 | [step from workflows] | n/a — user-approved skip | [reason] |

### Remaining Work
[What's still to do, or "None — all work complete"]

### Discovered Work
| Item | Recorded In |
|------|-------------|
| [description] | bead:ID / issue:#N / memory / backlog |

Omit sections that are genuinely empty (no PRs, no discovered work). But you must always include Objective, Verification Checklist, and Remaining Work.

Source Dependency

The canonical checklist lives in <verification-checklist> in shared instructions — always loaded, always available. Tool extensions provide the "how" (which skills/agents implement each step). Project config and memory can add or override steps.

If <verification-checklist> is missing from your loaded instructions, warn the user — the shared instruction files may not be installed. Fall back to tool extensions and memory, but flag the gap.

Red Flags — STOP

If any of these thoughts cross your mind, you're rationalizing:

Quick Reference