Verify Task
Run a task's verification checks and evaluate the results — no CLI required.
Instructions
The user's query is in $ARGUMENTS (a task ID like 077).
Find the task file:
- Read
.taskmd.yamlfor customdir(default:tasks) - Use
Globfor<task-dir>/**/*$ARGUMENTS*.md - Read frontmatter to confirm the ID matches
- If not found, list available tasks
- Read
Read the task file and extract the
verifyfield from frontmatterIf no verify checks are defined: Inform the user that the task has no verification checks
Run each verification check:
For
bashtype checks- Execute the
runcommand via theBashtool - If
diris specified, run in that directory (relative to project root) - If
diris not specified, run in the project root - Pass: exit code 0
- Fail: non-zero exit code
For
asserttype checks- Read the
checktext — this is a human-readable assertion - Inspect the relevant codebase files using
Read,Glob, andGrepto evaluate whether the assertion holds - Pass: the assertion is satisfied based on code inspection
- Fail: the assertion is not satisfied, explain why
- Execute the
Report results:
Verification results for task <ID>: <title> ✓ [bash] go test ./internal/api/... -run TestPagination — PASSED ✗ [bash] npm test — FAILED (exit code 1) Output: ... ✓ [assert] Pagination links appear in the API response headers — PASSED Evidence: Found Link header in handlers.go:142 ✗ [assert] Page size defaults to 20 — FAILED Reason: Default page size is 10 in config.go:38 Overall: FAIL (2 passed, 2 failed)
See SPEC_REFERENCE.md (in the plugin root) for verify check format and types.