acceptance

Coordinate parallel end-to-end checks against specs and acceptance criteria.

23|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/kirich1409/krozov-ai-tools --skill acceptance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow/skills/acceptance
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill acceptance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating end-to-end verification of changes by confirming implementations meet their specs or bugs are fully resolved, and presenting a single, consolidated acceptance receipt to guide downstream decisions.

Core Features & Use Cases

  • Parallel fan-out across specialized agents (manual-tester, code-reviewer, AC-coverage, design/a11y, security, performance, architecture, build-config, devops) to accelerate validation.
  • Unified receipt generation that aggregates verdicts, surfaces blockers, and enables routing to subsequent stages.
  • Flexible input resolution from spec frontmatter, test plans, and reproduction artifacts, with a re-verification loop that re-runs changed or failed checks.
  • Works for UI and non-UI projects, adapting fan-out based on spec and diff context, while preserving backward compatibility.

Quick Start

Invoke the acceptance skill to verify a change against its spec or confirm bug resolution and generate a consolidated acceptance receipt.

Frequently Asked Questions about acceptance

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

FAQPage Schema
How do I coordinate end-to-end verification for new features and bug fixes?

End-to-end verification is coordinated by orchestrating parallel checks against specs and acceptance criteria, collecting evidence, and producing a unified receipt. This applies to validating new features and confirming bug fixes across components.

What is a consolidated acceptance receipt and how does it guide downstream decisions?

A consolidated acceptance receipt aggregates verdicts from parallel validation checks and surfaces blockers. It provides a single unified document that enables routing implementations to subsequent development stages based on pass or fail outcomes.

Can I use multi-agent orchestration to verify both UI and non-UI project changes?

Multi-agent orchestration works for UI and non-UI projects by adapting its parallel fan-out based on spec and diff context. Specialized agents handle manual testing, code review, security, performance, and architecture validation.

How does deterministic re-verification work when tracking code changes?

Deterministic re-verification works by tracking diff_hash, spec_hash, and test_plan_hash. This allows the system to re-run only changed or previously failed checks, preserving backward compatibility while ensuring consistent validation outcomes.

What inputs do I need to resolve spec frontmatter and test plans for acceptance verification?

Acceptance verification resolves inputs flexibly from spec frontmatter, test plans, and reproduction artifacts. These inputs feed into parallel specialized agents that validate implementations against the defined acceptance criteria and specifications.