How do I install the Spec Verify skill?

Run npx skillmds@latest add jh941213/spec-verify-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Verify?

jh941213 (@jh941213) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Verify by jh941213 — Agent Skill

Name: Spec Verify
Author: jh941213

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.

jh941213 d4f014c 2.4 KB Updated Sep 17, 2026

File contents

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:

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

Step 3: Completion Report

When all items are complete:

## 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

## 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

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

---name: spec-verify-2description: 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.---# SPEC VerificationSkill for verifying completion after specification-based work.## Triggers- "spec verify", "spec-verify", "specification verification", "implementation verification"## Workflow### Step 1: Create Sub-AgentUse 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 FeedbackIf verification results show missing items:1. Show SPEC-REVIEW.md content to user2. Confirm whether to fix (use AskUserQuestion)3. If approved, implement missing items### Step 3: Completion ReportWhen 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 Principles1. **Objective verification**: Compare specification against actual implementation2. **Specific feedback**: "X feature's Y part is missing" instead of "not done"3. **Repeatable**: Feedback -> fix -> re-verify cycle

Frequently asked questions