home / skills / openclaw / skills / verify-task

verify-task skill

/skills/arisylafeta/clawlist/verify-task

This skill verifies completion of multi-step tasks against the original plan, ensuring quality criteria are met and documenting outcomes.

npx playbooks add skill openclaw/skills --skill verify-task

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.3 KB

---
name: verify-task
description: "MUST use after completing any multi-step task or project. Verifies completion against the original plan, checks quality criteria, and documents outcomes."
---

# Verify Task

## Overview

Confirm successful completion and document outcomes against the original plan.

## When to Verify

- All tasks from plan are marked complete
- User asks "is it done?" or "did it work?"
- Before declaring a project finished
- After each checkpoint in long-running tasks

## Verification Process

### Step 1: Load Original Plan

Read the plan that was created by write-plan skill.

### Step 2: Verify Each Checkpoint

Go through each checkpoint and confirm:
- [ ] All tasks marked complete
- [ ] Verification criteria met
- [ ] Quality standards achieved

### Step 3: Final Quality Checks

**General quality criteria:**
- [ ] Output matches original goal
- [ ] No obvious errors or issues
- [ ] Documentation updated (if applicable)
- [ ] User can use/access the result

### Step 4: User Confirmation

```
"Verification complete. Final checks:

✓ All tasks from plan completed (X/Y)
✓ Quality criteria met
✓ [Specific checks]

[Preview/demonstrate result]

Does this meet your expectations? Any adjustments needed?"
```

### Step 5: Document Completion

Save completion report to: `memory/plans/YYYY-MM-DD-<project>-complete.md`

Template:
```markdown
# [Project] - Completion Report

**Date Completed:** YYYY-MM-DD
**Original Goal:** [from plan]
**Final Result:** [brief description]

## Completion Summary

| Metric | Planned | Actual |
|--------|---------|--------|
| Checkpoints | X | X |
| Tasks | Y | Y |
| Time | Z min | W min |

## Verification Checklist

- [x] All tasks complete
- [x] Quality criteria met
- [x] User approved

## What Was Delivered

[Description of final output]

## Blockers Encountered

1. [Blocker] → [Resolution]

## Lessons Learned

- [What worked well]
- [What to do differently next time]
```

## Handling Issues

### If verification fails:

**Minor issues:** Quick fixes, proceed
**Major issues:** Return to doing-tasks or re-plan

## Principles

- **Objectivity** - Verify against the plan, not assumptions
- **Thoroughness** - Check all criteria
- **Honesty** - Report issues, don't hide problems
- **User-centric** - Final approval comes from user satisfaction

Overview

This skill verifies completion of multi-step tasks or projects against the original plan, checks quality criteria, and documents outcomes. Use it immediately after finishing work or at checkpoints to confirm everything meets the plan and user expectations. It produces a clear completion report and guides next steps if issues are found.

How this skill works

The skill loads the original plan and iterates through each checkpoint to confirm tasks are marked complete and verification criteria are satisfied. It runs final quality checks (output alignment, error review, documentation, access) and prompts the user for final confirmation. After approval, it saves a structured completion report to memory with metrics, blockers, and lessons learned.

When to use it

Right after completing any multi-step task or project
When a user asks “is it done?” or requests status
Before declaring a project finished or shipping deliverables
After each checkpoint in long-running tasks
When you need an audit trail or completion record

Best practices

Keep the original plan accessible and versioned so verification is objective
Define clear, measurable quality criteria in the plan before starting
Run verification in a quiet environment to reproduce and inspect outputs reliably
Log any deviations, blockers, and resolutions immediately for transparency
Get explicit user approval before marking a project complete

Example use cases

Finalize a content batch: verify all drafts, edits, and publishing steps completed and documented
Complete a software feature: confirm tests, deployments, and documentation are in place
Wrap up a data analysis project: check datasets, notebooks, visualizations, and access control
Close a design sprint: ensure assets, specifications, and handoff notes match the brief
Archive a project: validate backups, metadata, and completion report saved to memory

FAQ

What if the original plan is missing or incomplete?

Reconstruct the plan from available checkpoints and user input, document the reconstruction, then run verification against that reconstructed plan.

How are minor vs major issues handled?

Minor issues get quick fixes and verification continues. Major issues trigger a return to doing-tasks or re-planning and a clear note in the completion report.

Where is the completion report stored?

Reports are saved to a dated file in memory (memory/plans/YYYY-MM-DD-<project>-complete.md) so they can be audited or referenced later.