skills.rest
wahidyankf
wahidyankfCOMMUNITY
Explore all skills by this author →
𝕏@wahidyankfGitHub

plan-writing-gherkin-criteria

Enforce structured Given-When-Then syntax for testable acceptance criteria.

3|1|Updated Apr 18, 2026
Search Tags:#bdd#gherkin#user-stories#acceptance-criteria#given-when-then#test-scenarios#testable-requirements
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill plan-writing-gherkin-criteria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing-gherkin-criteria
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/plan-writing-gherkin-criteria
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill plan-writing-gherkin-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of writing ambiguous, non-testable acceptance criteria that cause misalignment between product teams, engineers, and QA, ensuring all requirements are clear, verifiable, and consistently understood across stakeholders.

Core Features & Use Cases

  • Structured Gherkin Syntax Guidance: Enforces the mandatory Given-When-Then structure and step-keyword cardinality hard rule to create valid, consistent acceptance criteria.
  • Pre-Built Domain Patterns: Includes ready-to-use patterns for common use cases including authentication, CRUD operations, form validation, error handling, and API response testing, plus advanced features like Background blocks and Scenario Outlines with Examples tables.
  • Best Practice & Error Prevention: Covers critical guidelines for scenario independence, declarative writing style, avoiding UI coupling, and eliminating common mistakes that lead to flaky or unmaintainable test suites.
  • Use Case: For example, a product manager can use this Skill to write acceptance criteria for a new user registration feature that developers can directly translate into automated Cucumber tests, eliminating guesswork and rework.

Quick Start

Use the plan-writing-gherkin-criteria skill to draft Given-When-Then acceptance criteria for the new password reset feature.

Frequently Asked Questions about plan-writing-gherkin-criteria

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

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

To write testable Gherkin acceptance criteria, enforce structured Given-When-Then syntax to eliminate ambiguous requirements. This ensures software features are clear, verifiable, and consistently understood across product, engineering, and QA stakeholders.

What is the best way to structure Given-When-Then scenarios for automated tests?▼

The best way to structure Given-When-Then scenarios is using declarative writing style and ensuring scenario independence. This prevents UI coupling and eliminates common mistakes that lead to flaky, unmaintainable automated test suites.

Can I use Gherkin Scenario Outlines and Background blocks for API response testing?▼

Yes, you can use Gherkin Background blocks and Scenario Outlines with Examples tables for API response testing. Pre-built domain patterns are included for common use cases like authentication, CRUD operations, form validation, and error handling.

Does this approach work for both web and mobile feature requirement specifications?▼

Yes, this approach works for web, mobile, and backend feature requirement specifications. It satisfies the need for standardized, business-readable specifications that map directly to automated test suites across different system architectures.

Why should product managers use Gherkin syntax for feature requirements?▼

Product managers should use Gherkin syntax for feature requirements because it allows developers to directly translate specifications into automated Cucumber tests. This eliminates guesswork and reduces rework caused by non-testable acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
alexsandrocruzalexsandrocruz

requirements-engineering

Convert stakeholder needs into structured, testable specifications with templates.

Community
Basic
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

bdd-assistant

Guide BDD workflows by creating Gherkin scenarios and step definitions.

Community
Intermediate
phatnguyen975phatnguyen975

use-case-testing

Derive executable test cases from use case specifications with preconditions and expected results.

Community
Advanced