gherkin-authoring
Use when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data Tables, tags, or Gherkin emb
SKILL.md.codex/skills/gherkin-authoring/SKILL.md
GitHubGherkin Authoring
Use this optional skill only after recommendation and user consent.
Write Gherkin as executable examples of business behavior. Optimize for domain language, concrete examples, and observable outcomes.
Workflow
- Identify the Gherkin region or acceptance-criteria section.
- Preserve surrounding Markdown unless explicitly asked to rewrite it.
- Clarify initial state, event, and observable outcome.
- Choose the smallest useful structure:
Feature, optionalRule,Background,Scenario,Scenario Outline, orExamples. - Keep scenarios short, usually 3-5 steps.
- Review syntax, duplicate steps, outcome observability, tables, and doc strings before returning.
Rules
Givenis state, not user interaction.Whenis one meaningful event.Thenis externally observable outcome.- Avoid UI clicks, HTTP calls, database rows, queues, and mocks unless they are the actual domain contract.
- Use two-space indentation unless preserving existing style.
- Escape
|as\|, newline as\n, and backslash as\\in tables.