Skip to content
Skills Library
Programming · Review & audit

plan-verify

/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.

Repository
vmark ↗
Licence
ISC
Last repository change
20.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

ISC, otwarta.

What it does and when to use it

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.

Original author description

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 it works

  1. Overview
  2. Workflow (Verify)
  3. Output Format (required)
  4. Verification Rules
Original SKILL.md headings · 50 lines, 199 words
SKILL.md preview
---
name: plan-verify
description: 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.
---

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

Versions

RepositoryScoreLicence
This page · xiaolai/vmark90ISC
dilhanz/ship100MIT

Database snapshot: 13.11.2026 · package version 71e9d94197dc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100verify-acceptance-criteria
    Use when asked to "verify acceptance criteria", "check criteria", or "verify the implementation against the plan" during active feature development. Do NOT trigger for issue management (close issue, comment), worktree cleanup, or post-merge/post-PR operations.
  • 100verify
    Use when a feature build is complete and needs verification against acceptance criteria and adversarial testing
  • 95aif-verify
    Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
  • 90plan-audit
    Audit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.
  • 100acceptance-check
    Standalone acceptance check — validates AC from PRD against code without full /implement pipeline. Use when the user says "check acceptance", "validate AC", "verify acceptance", "acceptance gate", or needs to verify acceptance criteria for a PR or external contribution.
  • 90dev10x:verify-acc-dod
    Verify that definition-of-done / acceptance criteria are met before closing a task list. Loads executable checks from plugin defaults, applies project overrides (add/remove/replace), runs each check automatically, and prompts the user only for manual items. TRIGGER when: task…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.