plan-writing-gherkin-criteria

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.