acceptance-validator

Validate code implementations against Gherkin acceptance criteria using Playwright, API, and manual tests.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/efiadm/informatik-ai-studio --skill acceptance-validator-efiadm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-validator
Source: https://github.com/efiadm/informatik-ai-studio/tree/main/.claude/skills/acceptance-validator
Command: npx skills add https://github.com/efiadm/informatik-ai-studio --skill acceptance-validator-efiadm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a quality gatekeeper, ensuring that code implementations meet predefined acceptance criteria before merging, thereby reducing bugs and improving overall product quality.

Core Features & Use Cases

  • Define Acceptance Criteria: Automatically generate Gherkin-based acceptance criteria for features.
  • Validate Implementations: Execute tests (Playwright, API, Manual) against defined criteria to verify code quality.
  • Use Case: Before merging a new user authentication feature, use this Skill to define its acceptance criteria (e.g., successful login, password reset) and then to validate that the implemented code passes all these criteria.

Quick Start

Use the acceptance-validator skill to define acceptance criteria for the user_authentication feature.

Frequently Asked Questions about acceptance-validator

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

FAQPage Schema
How do I validate code implementations against predefined acceptance criteria?

Validate code implementations by executing dynamic tests against predefined acceptance criteria using Gherkin syntax. This supports Playwright for E2E, API-Test for backend, and Manual-Only checklists to ensure adherence to quality standards before code merge.

How do I generate Gherkin-based acceptance criteria for a new feature?

Generate Gherkin-based acceptance criteria for features automatically to define quality standards. You can establish these criteria for specific features like user authentication to verify successful login and password reset scenarios.

Does the acceptance validation process support Playwright and API testing?

Acceptance validation supports Playwright for E2E testing, API-Test for backend validation, and Manual-Only checklists. These dynamic testing methods verify that implemented code passes all defined quality criteria.

What is the best way to automate quality assurance before merging code?

Automate quality assurance by using a quality gatekeeper that checks code implementations against predefined acceptance criteria. This reduces bugs and improves overall product quality by validating code before merging.

Can I use manual checklists alongside automated testing for quality validation?

Manual-Only checklists are supported alongside automated testing methods for quality validation. You can combine manual checks with Playwright E2E and API-Test backend validation to ensure comprehensive coverage of acceptance criteria.

Why should I use Gherkin syntax for defining software acceptance criteria?

Gherkin syntax structures predefined acceptance criteria for automated validation against code implementations. This ensures adherence to quality standards and reduces bugs before code merge by standardizing test scenarios.