acceptance

Validate blueprint implementations against acceptance criteria and record verdicts.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill acceptance-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance
Source: https://github.com/jfmyers9/agent/tree/main/skills/acceptance
Command: npx skills add https://github.com/jfmyers9/agent --skill acceptance-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that a target blueprint's implementation meets its acceptance criteria and records a formal verdict in a review blueprint for traceability.

Core Features & Use Cases

  • Resolve target blueprint and read acceptance criteria from plan/spec sections
  • Execute a two-pass verification: Verifier pass to check criteria, Breaker pass to surface edge cases and gaps
  • Store results into a new or updated review blueprint with evidence and rationale
  • Supports an automatic fix plan generation when --auto is requested

Quick Start

Run a target acceptance check against the current blueprint to generate a review.

Frequently Asked Questions about acceptance

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

FAQPage Schema
How do I verify if a blueprint implementation meets its acceptance criteria?

Acceptance verification works by executing a two-pass validation: a verifier pass checks if criteria are met, and a breaker pass surfaces edge cases and gaps. Results are stored in a review blueprint with evidence and rationale for full traceability.

What's the best way to automate code review and quality assurance for spec validation?

Automating spec validation requires aggregating criteria from blueprint sections and running automated verification passes. An optional auto-fix mode can generate fix plans automatically when issues are found during the acceptance review process.

How does the breaker pass work during acceptance verification?

The breaker pass works as the second stage of acceptance verification, specifically designed to surface edge cases and gaps that the initial verifier pass might miss. It complements the criteria check by stress-testing the implementation boundaries.

Do I need blueprint tooling to run acceptance checks on specs and plans?

Yes, blueprint tooling is required. The verification process needs access to plan, spec, and review criteria within the blueprint structure to create and attach a completed acceptance review with a formal verdict.

Can I automatically generate fix plans when acceptance verification finds issues?

Yes, you can automatically generate fix plans by requesting the auto-fix option during acceptance verification. When issues are found during the verifier and breaker passes, the system generates an automatic fix plan to address the identified gaps.

Why should I use blueprint-based acceptance verification instead of manual code review?

Blueprint-based acceptance verification provides traceability by recording formal verdicts with evidence in a review blueprint. Unlike manual review, it systematically aggregates criteria from spec and plan sections and runs structured verifier and breaker passes to catch edge cases.