skills.rest
SSiertsema
SSiertsemaCOMMUNITY
Explore all skills by this author →
GitHub

acceptance-criteria-writing

Generate and validate acceptance criteria for user stories across systematic scenarios.

1|Updated Nov 29, 2025
Search Tags:#quality-assurance#invest#gherkin#acceptance-criteria#test-design#story-splitting
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill acceptance-criteria-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acceptance-criteria-writing
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/acceptance-criteria-writing/skills/acceptance-criteria-writing
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill acceptance-criteria-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and auditing acceptance criteria for user stories is time-consuming and error-prone; this Skill provides a structured approach to generate comprehensive, testable ACs with systematic coverage.

Core Features & Use Cases

  • Systematic coverage across happy path, negative, edge, boundary, accessibility, and performance
  • INVEST verification per story
  • SPIDR-based splitting for oversized stories

Use Case: A product team can rapidly produce acceptance criteria that are measurable, testable, and ready for automation or manual testing.

Quick Start

Provide a user story or requirement and optional mode (write / audit / split) to generate structured acceptance criteria.

Frequently Asked Questions about acceptance-criteria-writing

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

FAQPage Schema
How do I write testable acceptance criteria for user stories?▼

You can automatically generate acceptance criteria by providing a user story or requirement, which produces structured ACs covering happy path, negative, edge, boundary, accessibility, and performance scenarios for manual or automated testing.

How do I verify if a user story meets INVEST principles?▼

Verifying INVEST principles for a user story involves auditing its independence, negotiability, value, estimability, size, and testability. This Skill audits provided stories against these criteria to confirm they are properly structured for development.

What is the best way to split oversized user stories?▼

The best way to split oversized user stories is using the SPIDR method. This Skill applies SPIDR-based splitting to break down large stories into smaller, manageable units that maintain systematic test coverage and INVEST compliance.

Can I audit existing acceptance criteria for edge and boundary scenarios?▼

Yes, you can audit existing acceptance criteria by providing them in audit mode. This validates the ACs for comprehensive coverage, identifying missing negative, edge, boundary, accessibility, and performance scenarios within the current requirements.

Does this acceptance criteria generator support Gherkin syntax output?▼

Yes, the acceptance criteria generator supports Gherkin syntax. It structures the generated happy path, negative, and edge scenarios to align with Gherkin formats, making them ready for test design and automation frameworks.

Related Skills

Explore More Software Engineering Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
hmctshmcts
3

generate-bdd-specs

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

Official
Intermediate
serejarisserejaris
215

pm-user-stories

Break Epics into INVEST-validated user stories with acceptance criteria and a Story Map.

Community
Advanced
Chris-MaskeyChris-Maskey

user-story-fundamentals

Capture user-centered product requirements as structured user stories.

Community
Intermediate