ac-to-examples

Convert Given-When-Then acceptance criteria into concrete testable examples.

5|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/tikazyq/agentic-spec-forge --skill ac-to-examples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ac-to-examples
Source: https://github.com/tikazyq/agentic-spec-forge/tree/main/AGENTIC_SPEC_FORGE/spec_stage_skill/requirements/ac-to-examples
Command: npx skills add https://github.com/tikazyq/agentic-spec-forge --skill ac-to-examples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms abstract Acceptance Criteria (ACs) written in a Given-When-Then format into concrete, easy-to-understand examples with specific data and steps, making them accessible to non-technical stakeholders and directly usable for manual testing.

Core Features & Use Cases

  • Concrete Examples: Converts abstract conditions (e.g., "valid credentials") into specific data (e.g., "email: [email protected], password: Pass123!").
  • Actionable Steps: Breaks down abstract actions (e.g., "submit login") into detailed, sequential operations (e.g., "1. Enter email, 2. Enter password, 3. Click login").
  • Observable Results: Clarifies abstract outcomes (e.g., "show success message") into verifiable phenomena (e.g., "green banner at top displays 'Login successful...'").
  • Use Case: A Product Manager has written ACs for a new feature, but the QA team finds them too vague to test. This Skill generates specific test data and steps for each AC, allowing QA to immediately start manual testing and the PM to easily verify the expected outcomes.

Quick Start

Use the ac-to-examples skill to generate concrete examples for the acceptance criteria in the requirements document.

Frequently Asked Questions about ac-to-examples

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

FAQPage Schema
How do I convert abstract acceptance criteria into concrete manual testing examples?

To convert abstract acceptance criteria into concrete manual testing examples, transform Given-When-Then formats by injecting specific business data, sequential actionable steps, and verifiable observable results for non-technical stakeholders.

What is the best way to make BDD acceptance criteria testable for QA teams?

Making BDD acceptance criteria testable involves translating abstract conditions like valid credentials into specific test data and breaking down actions into step-by-step operations, ensuring QA teams can immediately start manual testing.

How do I generate specific test data from vague Given-When-Then requirements?

Generating specific test data from vague Given-When-Then requirements requires replacing abstract parameters with explicit business-language values, such as changing valid credentials to exact email and password strings for direct testing.

Can I clarify abstract acceptance criteria outcomes for non-technical stakeholders?

Yes, you can clarify abstract acceptance criteria outcomes for non-technical stakeholders by converting general statements like show success message into observable phenomena such as a green banner displaying a specific login successful text.

Does this approach to acceptance criteria generation support requirements written outside the Given-When-Then format?

No, this approach to acceptance criteria generation specifically targets requirements written in the Given-When-Then format, transforming those abstract conditions, actions, and results into directly testable manual scenarios.