# Spec Verify

> Verifies implementation completeness against SPEC.md specification. Triggers on: spec verify, spec-verify, specification verification, implementation verification. NOT for: code review, unit tests, build verification.

- Skill: `jh941213/spec-verify-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jh941213/spec-verify-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jh941213/spec-verify-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jh941213 (https://skillmd.com/u/jh941213)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jh941213/spec-verify-2

---


# SPEC Verification

Skill for verifying completion after specification-based work.

## Triggers
- "spec verify", "spec-verify", "specification verification", "implementation verification"

## Workflow

### Step 1: Create Sub-Agent

Use the **Task tool** to create a verification agent:

```
subagent_type: "Explore"
prompt: |
  Read the SPEC.md file and verify the following:

  1. Check whether all specification requirements have been implemented
  2. Check each item:
     - [ ] Functional requirements
     - [ ] Non-functional requirements
     - [ ] UI/UX specification
     - [ ] API design (if applicable)
     - [ ] Security considerations

  3. Specifically identify any missing items
  4. Include improvement suggestions

  Return the results as text. (The Explore sub-agent is read-only — do not write files.)
```

The sub-agent returns its results as text; writing the returned results to the SPEC-REVIEW.md file is done by this skill (the parent).

### Step 2: Address Feedback

If verification results show missing items:

1. Show SPEC-REVIEW.md content to user
2. Confirm whether to fix (use AskUserQuestion)
3. If approved, implement missing items

### Step 3: Completion Report

When all items are complete:

```markdown
## Verification Complete

### Implementation Status
- [x] Functional requirements: 100%
- [x] Non-functional requirements: 100%
- [x] UI/UX: 100%
- [x] Tests: 100%

### Notes
- ...

### Suggested Next Steps
- ...
```

## Verification Checklist

```markdown
## SPEC Verification Checklist

### Feature Completeness
- [ ] All functional requirements implemented
- [ ] All edge cases handled
- [ ] Error handling is adequate

### Code Quality
- [ ] Type safety ensured
- [ ] Lint rules followed
- [ ] Test coverage sufficient

### Documentation
- [ ] Code comments adequate
- [ ] API documentation (if applicable)
- [ ] README updated

### Security
- [ ] Input validation
- [ ] Authentication/authorization verified
- [ ] Sensitive data protected
```

## Core Principles

1. **Objective verification**: Compare specification against actual implementation
2. **Specific feedback**: "X feature's Y part is missing" instead of "not done"
3. **Repeatable**: Feedback -> fix -> re-verify cycle