Verify Task

Verify explicit requirements and coverage against a fixed implementation scope using discovered repository-native gates. Reports missing, failed, or stale evidence; never fixes code or changes tracking.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add flurdy/agent-skills --skill verify-task
Manual install
git clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/verify-task ~/.claude/skills/verify-task

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Verify Task

Own requirements satisfaction, coverage sufficiency, and execution evidence for a fixed change.
This is a non-repairing verification pass: no source edits, tracking writes, checkout changes,
installation, commits, or publication. No automatic fixes. Test commands may create normal ignored
generated output, but that is not permission to rewrite source, snapshots, lockfiles, or config.

`architect` owns design, `develop` / `implement-solution` own authorized changes, `pedantic-review`
owns craft/test design, and `second-opinion` supplies advisory independent claims. This skill does
not duplicate those reviews or infer correctness from their approval. `complete-task` may normally
finalize only after requirements, applicable evidence, and current-scope stability are established.
The narrowly qualified future-event handoff in §6 permits a tracking disposition, not a verification
pass or waiver of failed checks.

## Usage

```text
/verify-task <bead-selector or explicit request>
/verify-task                         # use the current task and supplied scope when unambiguous
```

Honor the premium route. If reduced capability is known, disclose it and ask to continue or stop,
unless the user explicitly chose it. Do not invent model IDs or switch routes merely for ceremony.

## 1. Identify requirements and ownership

Prefer the caller's explicit requirements and supplied scope. A composing workflow such as
Read the full skill on GitHub

Details

Skill name
verify-task
Path
skills/verify-task/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Verify Task skill do?

Verify explicit requirements and coverage against a fixed implementation scope using discovered repository-native gates. Reports missing, failed, or stale evidence; never fixes code or changes tracking.

How do I install the Verify Task skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill verify-task. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Verify Task popular?

It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.