skills.rest
SensLiao
SensLiaoCOMMUNITY
Explore all skills by this author →
GitHub

i2r-acceptance-mode

Convert functional requirements JSON into Gherkin scenarios and prose acceptance criteria.

Updated May 28, 2026
Search Tags:#acceptance criteria#software testing#automated testing#functional requirements#gherkin
One-click install
npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-acceptance-mode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i2r-acceptance-mode
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/i2r-acceptance-mode
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-acceptance-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of Gherkin scenarios and prose acceptance criteria from functional requirements, streamlining the software testing process.

Core Features & Use Cases

  • Scenario Generation: Converts functional requirements into machine-readable Gherkin Given/When/Then scenarios.
  • Prose Creation: Produces plain English prose descriptions of scenarios for integration with product requirements documents.
  • Use Case: When a new feature is added to a project, use this Skill to generate the necessary acceptance tests and acceptance criteria documentation.

Quick Start

Load the 04-functional.json file into the i2r-acceptance-author agent for Stage 6.

Frequently Asked Questions about i2r-acceptance-mode

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

FAQPage Schema
How do I generate Gherkin acceptance scenarios from functional requirements?▼

To generate Gherkin acceptance scenarios from functional requirements, you can use this Skill to convert functional requirements JSON into machine-readable Given/When/Then scenarios for software testing.

Can I automatically create acceptance criteria for automated testing?▼

Yes, you can automatically create acceptance criteria for automated testing by processing a functional requirements JSON file to produce both Gherkin scenarios and plain English prose descriptions.

What is the best way to document acceptance scenarios for product requirements?▼

The best way to document acceptance scenarios for product requirements is to generate plain English prose descriptions alongside Gherkin scenarios, ensuring integration with product requirements documents.

Do I need a specific agent workflow to convert functional requirements into Gherkin?▼

Yes, converting functional requirements into Gherkin requires the i2r-acceptance-author agent workflow, where you load a functional requirements JSON file to process acceptance scenario generation.

What format does the automated testing output use when generating acceptance criteria?▼

The automated testing output uses a JSON format, which is produced by processing the input functional requirements JSON specifically for automated testing workflows.

Related Skills

Explore More Software Engineering Skills→
Mte90Mte90
51

Product Requirements

Draft Product Requirements Documents through a structured Q&A process.

Community
Advanced
hmctshmcts
3

generate-bdd-specs

Converts acceptance criteria into Cucumber/Gherkin feature files with backgrounds and tags.

Official
Intermediate
CAPHTECHCAPHTECH
1

spec-observation

Identify specification ambiguities and formalize acceptance criteria in Given/When/Then format.

Official
Advanced
archibatearchibate
103

defining-requirements

Translate user needs into testable user stories with Gherkin acceptance criteria.

Community
Intermediate