verify-task

Verifies completed tasks against the original plan and documents outcomes in completion reports.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill verify-task-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-task
Source: https://github.com/Tgoldi/claude-skills/tree/main/verify-task
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill verify-task-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a multi-step task or project, it is easy to declare success without actually checking the work against the original plan. This Skill enforces a structured verification pass so nothing is marked done without meeting the planned criteria. ## Core Features & Use Cases - Plan-Based Verification: Loads the plan created by the write-plan skill and checks every checkpoint and task for completion. - Quality Checklist: Confirms output matches the original goal, has no obvious errors, and is usable by the requester. - Completion Documentation: Saves a structured completion report to memory/plans/ with metrics, blockers, and lessons learned. - Use Case: After finishing a multi-day refactoring project, run verification to confirm all checkpoints passed, present the result to the user for approval, and archive a completion report for future reference. ## Quick Start Verify that the project we just finished meets all the checkpoints in the original plan and write a completion report.

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 is actually complete in Claude Code?

Use the verify-task skill after finishing a multi-step task. It loads the original plan, checks each checkpoint and task against quality criteria, presents the result for your confirmation, and documents the outcome.

What should I check before declaring a project finished?

Confirm all planned tasks are marked complete, verification criteria are met, output matches the original goal, and documentation is updated. The verify-task skill walks through this checklist and asks for your final approval.

Does verify-task work without a written plan?

It is designed to read a plan created by the write-plan skill, so it works best when a plan file exists. Without one, verification falls back to general quality criteria rather than checkpoint-by-checkpoint confirmation.

What happens if verification fails?

Minor issues are fixed quickly and verification proceeds. Major issues send the work back to task execution or trigger re-planning, so problems are reported honestly instead of being hidden.

Where are completion reports saved?

Completion reports are saved as Markdown files to memory/plans/ with the naming pattern YYYY-MM-DD-<project>-complete.md. Each report includes metrics, a verification checklist, blockers encountered, and lessons learned.