# Verification Strategy

Thorough verification of completed work before declaring done

- Repository: https://github.com/vstorm-co/pydantic-deepagents (1111 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -g -a claude-code -y`
Codex: `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -g -a codex -y`
Cursor: `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -g -a cursor -y`
Gemini CLI: `npx skills add vstorm-co/pydantic-deepagents --skill verification-strategy -g -a gemini-cli -y`

## Description

Thorough verification of completed work before declaring done

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Verification Strategy

How to verify your work is correct before declaring a task complete.

## The Verification Checklist

After implementing a solution, go through ALL of these:

### 1. Re-read the original task
- Re-read the EXACT wording of the task instruction
- Check every requirement, file paths, names, formats, constraints
- Are there implicit requirements? ("compile with gcc -O3 -lm" means exact flags)

### 2. Check file outputs
- Do all required files exist at the exact paths specified?
- Are file sizes within any stated limits?
- Is the file format correct? (binary vs text, encoding, line endings)

```bash
ls -la /path/to/expected/output
wc -c /path/to/output    # byte count
file /path/to/output      # format detection
head -5 /path/to/output   # content preview
```

### 3. Compile and run
- Compile with the EXACT flags specified in the task
- Run with the EXACT command and arguments specified
- Check exit code: `echo $?` (should be 0 for success)
- Check both stdout AND stderr

### 4. Validate output
- Compare output against expected format
- Check exact field names, delimiters, number formatting
- If the task specifies output format, match it exactly:
  - JSON: valid JSON? correct schema?
  - CSV: correct headers? correct delimiter?
  - Plain text: correct line endings? trailing newline?

### 5. Test edge cases
- Empty input (if applicable)
- The specific test inputs mentioned in the task
- Large inputs (if the task involves performance)

### 6. Check constraints
- Size limits (file size, code length)
- Time limits (does it finish in reasonable time?)
- Memory limits (does it stay within bounds?)
- No external dependencies that aren't available

## Reading Test Scripts

If you can find the test script, READ IT:
- What exact assertions does it make?
- What inputs does it use?
- What output format does it expect?
- What timeouts are set?

The rest: https://github.com/vstorm-co/pydantic-deepagents/blob/HEAD/apps/cli/skills/verification-strategy/SKILL.md