verify-task

Verifies completed tasks against acceptance criteria with fresh test runs and independent reviews.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill verify-task-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-task
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/verify-task
Command: npx skills add https://github.com/toderian/project_template --skill verify-task-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished tasks often claim success without evidence: tests were never re-run, acceptance criteria quietly changed mid-task, or implemented code is a stub that nothing calls. This Skill audits a completed task against its own task file and produces a per-criterion verdict backed by evidence. ## Core Features & Use Cases - Goal-backward criterion checks: Each acceptance criterion is verified in three steps — the artifact exists, is substantive (no stubs or TODO placeholders), and is wired into the codebase — with path:line evidence recorded per step. - Criteria drift detection: Compares the task file's git history to find criteria that were changed, added, or removed during the work, and flags any change the execution log does not explain. - Fresh test execution and independent review: Re-runs all related tests and the repo check command, then dispatches spec-blind validator and reviewer subagents over the full diff. - Use Case: Before completing a multi-phase task like AUTH-001, run verification to confirm every acceptance criterion is met, tests pass fresh, and no scope creep occurred — then append the verdict to the task's execution log. ## Quick Start Ask the agent to verify task AUTH-001 to check whether its acceptance criteria were actually implemented correctly.

Frequently Asked Questions about verify-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a task was implemented correctly?

Run the verify-task skill with the task ID or path. It re-runs the task's related tests fresh, checks each acceptance criterion for existence, substance, and wiring in the code, and reports a per-criterion verdict of MET, NOT MET, or UNVERIFIABLE.

How to detect acceptance criteria that changed during a task?

The skill walks the task file's git history and diffs checklist text per commit, classifying each criterion as unchanged, changed-during-task, or added-during-task. Changes not explained by the execution log are reported as findings.

Does task verification modify the repository or task file?

No. Verification is report-only: it appends a single execution-log entry with the verdict and recommendation, and changes nothing else. It never ticks checkboxes or edits code; fixing gaps is a separate decision.

What happens when a test cannot be run during verification?

A test that cannot run is marked UNVERIFIABLE with the reason recorded. Any UNVERIFIABLE criterion or unexplained criteria drift forces the overall verdict to HUMAN_NEEDED rather than PASS or GAPS.

When should I run task verification?

Run it before completing any task with more than one phase or an execute-plan run, on an archived task whose outcome is in doubt, or whenever you ask whether a task ID was implemented correctly.