acceptance-testing

Transform requirements into acceptance criteria, test scenarios, and a UAT plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terraphim/terraphim-skills --skill acceptance-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-testing
Source: https://github.com/terraphim/terraphim-skills/tree/main/skills/acceptance-testing
Command: npx skills add https://github.com/terraphim/terraphim-skills --skill acceptance-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams plan and execute user acceptance tests (UAT) by translating requirements or stories into acceptance criteria, test cases, test data, and a sign-off checklist; it also suggests automation options for web, CLI, and API workflows.

Core Features & Use Cases

  • Structured Criteria Derivation: Convert each requirement into positive, negative, and non-functional acceptance criteria.
  • Scenario Creation: Produce clear, actionable test scenarios (Gherkin or checklist) aligned to acceptance criteria.
  • Automation Guidance: Recommend automation strategies (Playwright/Cypress for web, golden tests for CLIs/APIs) and environment considerations.
  • UAT Plan & Sign-off: Generate a complete UAT plan template with ownership, environments, and a bug-report workflow.

Quick Start

Start by mapping user stories to acceptance criteria and drafting 2-3 high-value scenarios per feature. Then choose manual or automated execution and prepare a UAT plan template with owners and environments.

Frequently Asked Questions about acceptance-testing

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

FAQPage Schema
How do I write a UAT plan from user stories?

To create a UAT plan from user stories, translate each requirement into positive, negative, and non-functional acceptance criteria, then map them to clear test scenarios with designated owners and environments.

What is included in a user acceptance testing sign-off checklist?

A UAT sign-off checklist includes derived acceptance criteria, mapped test scenarios, designated owners, defined testing environments, and a structured bug-report template to formalize the release validation process.

How do I write acceptance criteria for web, CLI, and API workflows?

Write acceptance criteria for web, CLI, and API workflows by deriving positive, negative, and non-functional conditions from project requirements, then formatting them as actionable Gherkin scenarios or structured checklists.

Does this approach support automated E2E testing with Playwright or Cypress?

Yes, the workflow supports automated E2E testing by recommending specific automation strategies like Playwright or Cypress for web, and golden tests for CLI and API projects, integrated within the overall UAT plan.

Can I generate test scenarios in Gherkin format for manual testing?

Yes, you can produce test scenarios in Gherkin format or as standard checklists for manual UAT execution, ensuring each scenario directly aligns with the defined positive, negative, and non-functional acceptance criteria.

When should I use manual UAT instead of automated E2E tests?

Choose manual UAT over automated E2E tests when validating complex user workflows requiring human judgment and formal sign-off, whereas automated E2E testing is recommended for repetitive regression checks across web, CLI, and API projects.