skills.rest
uta2000
uta2000COMMUNITY
Explore all skills by this author →
GitHub

verify-acceptance-criteria

Compare codebase against plan acceptance criteria and produce a verdict report.

4|Updated Feb 7, 2026
Search Tags:#automation#verification#plan#code-review#acceptance-criteria#feature-flow#task-verifier
One-click install
npx skills add https://github.com/uta2000/feature-flow --skill verify-acceptance-criteria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-acceptance-criteria
Source: https://github.com/uta2000/feature-flow/tree/main/skills/verify-acceptance-criteria
Command: npx skills add https://github.com/uta2000/feature-flow --skill verify-acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mechanically verifies that an implementation satisfies the acceptance criteria defined in a plan by comparing the codebase against the documented criteria. Delegates verification to the task-verifier agent and reports results.

Core Features & Use Cases

  • Plan-driven verification: Checks implemented code against the acceptance criteria extracted from the project plan.
  • PR-conscious workflow: Verifies before PR creation and can skip if a PR already exists for the branch.
  • Delegated validation: Uses the task-verifier agent to perform the actual checks and to generate a structured verification report.
  • Optional plan updates: When all criteria pass, offers to update the plan to reflect verified items.

Quick Start

Run verify-acceptance-criteria after implementing tasks to confirm all acceptance criteria align with the plan.

Frequently Asked Questions about verify-acceptance-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically verify acceptance criteria against my codebase implementation?▼

Automated acceptance criteria verification compares your codebase against documented plan criteria using a delegated task-verifier agent, producing a structured verdict and report confirming alignment before PRs.

When should I run acceptance criteria verification during feature development?▼

Acceptance criteria verification should run during active feature development before PR creation, mechanically checking implemented code against extracted plan criteria to ensure alignment before releases.

Can I skip verification if a pull request already exists for my branch?▼

Yes, the PR-conscious verification workflow can skip the acceptance criteria checks if a pull request already exists for the current development branch.

What happens after all acceptance criteria pass the verification check?▼

When all acceptance criteria pass verification, the tool optionally offers to update the project plan file to reflect the verified items and mark them as complete.

How does the task-verifier agent validate feature flows in my code?▼

The task-verifier agent receives delegated validation instructions, compares the implementation against the plan's acceptance criteria, and generates a structured report detailing the verification verdict.

What is the best way to ensure plan-driven verification before submitting code reviews?▼

Plan-driven verification uses a task-verifier agent to mechanically compare your implementation against acceptance criteria extracted from the plan, ensuring feature flow alignment before code reviews.

Related Skills

Explore More Software Engineering Skills→
boomNDSboomNDS

writing-plans

Convert feature specifications into executable implementation plans with tasks and acceptance criteria.

Community
Basic
klhklh
9

code-review-and-quality

Review code across correctness, readability, architecture, security, and performance.

Community
Advanced
audunstrandaudunstrand

create-tasks

Generate INVEST-compliant engineering tasks with context, acceptance criteria, and verification.

Community
Advanced
subroh0508subroh0508
18

bug-fix

Analyze bug reports into reproduction steps, root-cause findings, and specification-gap assessments.

Community
Advanced