acceptance-testing

Define acceptance criteria and manage User Acceptance Testing workflows.

1|Updated Aug 10, 2025
One-click install
npx skills add https://github.com/michsindlinger/agent-os-extended --skill acceptance-testing-michsindlinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-testing
Source: https://github.com/michsindlinger/agent-os-extended/tree/main/agent-os/templates/skills/dev-team/po/acceptance-testing
Command: npx skills add https://github.com/michsindlinger/agent-os-extended --skill acceptance-testing-michsindlinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that developed features meet user needs and business requirements by providing a structured approach to defining acceptance criteria and executing User Acceptance Testing (UAT).

Core Features & Use Cases

  • Acceptance Criteria Definition: Define clear, testable criteria using formats like Given-When-Then or checklists.
  • Test Case Development: Structure comprehensive test cases with preconditions, steps, and expected results.
  • UAT Execution & Coordination: Plan, conduct, and manage UAT sessions, including defect tracking and sign-off.
  • Use Case: A Product Owner can use this skill to generate a detailed UAT plan for a new user registration feature, ensuring all acceptance criteria are covered before release.

Quick Start

Use the acceptance-testing skill to define acceptance criteria for the user login feature using the Gherkin format.

Frequently Asked Questions about acceptance-testing

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

FAQPage Schema
How do I write acceptance criteria using the Gherkin format for user acceptance testing?

Test case development for UAT involves structuring comprehensive scenarios with explicit preconditions, sequential execution steps, and expected results. This structured approach ensures all acceptance criteria are fully covered and validated before software release sign-off.

What is the best way to plan and coordinate User Acceptance Testing (UAT) execution?

UAT planning and coordination requires structuring test sessions, executing defined test cases, tracking discovered defects, and managing the final sign-off process. This systematic execution validates that developed features meet user needs and business requirements.

Can I use checklist-based acceptance criteria instead of Gherkin for requirements validation?

Checklist-based acceptance criteria are fully supported alongside Gherkin and scenario-based formats for requirements validation. This flexibility allows product owners to define testable conditions using whichever format best matches the specific feature being validated.

How do I manage defect tracking during User Acceptance Testing (UAT)?

Defect management during UAT involves coordinating test execution, tracking discovered issues against acceptance criteria, and resolving them before final sign-off. This structured defect tracking ensures features meet business requirements before release.

When do I need structured User Acceptance Testing (UAT) for my software features?

Structured UAT is needed when validating developed software features against user needs and business requirements prior to release. It provides a systematic approach to requirements validation through comprehensive test case execution and formal sign-off.