Plan Verify
Verify a completed implementation against a plan by running gates and checking acceptance criteria. Use when the user asks to verify work items or confirm completion.
Install
npx skills add lllyys/vreader --skill plan-verifygit clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/plan-verify ~/.claude/skills/plan-verifyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Plan Verify
## Overview
Runs the plan’s required tests/gates and validates acceptance criteria, producing a pass/fail verification report.
## Workflow (Verify)
1) **Locate the plan**
- Prefer `dev-docs/plans/<plan>.md`.
- If unclear, ask for the plan path.
2) **Extract verification checklist**
- For each WI, list:
- Acceptance criteria
- Required tests
- Manual checks (if any)
3) **Run gates**
- Use repo-specific gates from `.claude/commands/feature-workflow.md` or plan “Testing Procedures”.
- If tests are not runnable, note the blocker explicitly.
4) **Verify acceptance**
- For each WI, mark each acceptance criterion as Pass/Fail/Blocked.
- Include evidence (test output, file refs, manual steps).
5) **Report results**
- Summarize pass/fail with concrete next actions.
## Output Format (required)
- **Verification Summary**
- Total WIs verified
- Pass/Fail/Blocked counts
- **Gate Results**
- Command → status
- Failures with key error lines
- **Acceptance Matrix**
- WI‑### → criterion → Pass/Fail/Blocked
- **Manual Checks**
- Steps executed + outcome
## Verification Rules
- Always run tests unless the user explicitly forbids it.
- If tests are skipped or fail, mark WI as **Blocked**.
- Do not claim “verified” without test evidence.
- Manual checks must include evidence (step list + observed result).Details
- Skill name
plan-verify- Repository
- lllyys/vreader
- Path
.claude/skills/plan-verify/SKILL.md- Repo updated
- 6 August 2026
FAQ
What does the Plan Verify skill do?
Verify a completed implementation against a plan by running gates and checking acceptance criteria. Use when the user asks to verify work items or confirm completion.
How do I install the Plan Verify skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill plan-verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Plan Verify popular?
It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.
Related skills
AI Coding Agents
49lllyys/vreader
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Dispatch
49lllyys/vreader
Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.
Feature Workflow
49lllyys/vreader
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud
Power Word Kill
113Hmbown/Wizards-of-the-Ghosts
In D&D, Power Word Kill instantly destroys any creature below a hit-point threshold — no saving throw, no resistance, just death. The real-world version is kill -9: the unconditional termination signal. Emergency circuit breakers. Hard account terminations. The nuclear option that exists because sometimes graceful shutdown is not available and the cost of continuing is worse than the cost of data loss. Power Word Kill is not elegant. It is not kind. It is the thing you reach for when everything else has already failed.
Persuasion
113Hmbown/Wizards-of-the-Ghosts
Use this skill when the problem is not information scarcity but alignment, framing, or buy-in.
Profile
49hw-native-sys/simpler
Run an example ($ARGUMENTS) with profiling enabled on hardware and report the swimlane/timing breakdown. Use when the user asks to profile an example on hardware.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.