Fix
genkovich/sdd
A skill your agent uses to fix a reported bug spec-first: reproduce it, trace the symptom to the owning feature's acceptance criteria, pin it with a failing (RED) test, apply the minimal GREEN fix…
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…
Install Gherkin Authoring
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gherkin-authoring .claude/skills/gherkin-authoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .claude/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/gherkin-authoring .agents/skills/gherkin-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .agents/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/gherkin-authoring .cursor/skills/gherkin-authoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .cursor/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intent-driven-dev/intent-driven-template.git --path .agents/skills/gherkin-authoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/gherkin-authoring .gemini/skills/gherkin-authoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .gemini/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/gherkin-authoring .github/skills/gherkin-authoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .github/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intent-driven-dev/intent-driven-template gherkin-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/gherkin-authoring .opencode/skills/gherkin-authoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gherkin-authoring" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/gherkin-authoring into .opencode/skills/gherkin-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gherkin-authoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gherkin-authoring- GitHub stars
- 159
- Token cost
- ~1.4k tokens
- SKILL.md length
- 620 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…
- Works in 6 steps: Identify the Gherkin region: whole… → Preserve the surrounding wrapper unless… → Clarify the behavior as examples:… → …
- Improving Gherkin
- SKILL.md covers Overview, Scope, Workflow and Quick Reference, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Gherkin Authoring is an agent skill from intent-driven-dev/intent-driven-template. 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 embedded in Markdown.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering User stories. The repository describes itself as: OpenSpec and OpenCode template for intent-driven development with specs, ADRs, C4 diagrams, Gherkin, TDD, Multi-Model Adversarial Spec Authoring, Glossary for Domain Terms, and… The licence is MIT.
When your agent uses it
- Improving Gherkin
- Cucumber scenarios
- BDD acceptance criteria
- Feature examples
Example prompts
- “/gherkin-authoring”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify the Gherkin region: whole .feature file, fenced gherkin block, indented block, quoted acceptance criteria, or inline scenario text.
- Preserve the surrounding wrapper unless explicitly asked to change it. For Markdown input, return the heading/prose/fence context, not…
- Clarify the behavior as examples: initial state, event, observable outcome.
- Choose the smallest structure that expresses the behavior: Feature, optional Rule, Background, Scenario/Example, or Scenario Outline with…
- Keep scenarios concrete and short, usually 3-5 steps.
- Review syntax and readability before returning: colons, step keywords, duplicate step text, observable outcomes, and table/doc string…
What it can do on your machine
Read from SKILL.md and the folder at commit 73f54d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gherkin Authoring loads about 1.4k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 620 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from intent-driven-dev/intent-driven-template at commit 73f54d5, republished under its MIT licence (© intent-driven-dev). 620 words, ~1,388 tokens.
Download SKILL.mdSave it as
.claude/skills/gherkin-authoring/SKILL.md (or your agent's skills folder).- name
- gherkin-authoring
- description
- 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 embedded in Markdown.
Gherkin Authoring
Overview
Write Gherkin as executable examples of business behavior. Optimize for domain language, concrete examples, and observable outcomes; keep implementation and UI mechanics inside step definitions.
Scope
Use this for standalone .feature files and Gherkin embedded in Markdown or other prose. When Gherkin is inside a Markdown wrapper, review or rewrite only the Gherkin section unless the user asks for broader document edits. Preserve fences, headings, and surrounding prose. If the input includes Markdown around the Gherkin, return the Markdown wrapper with only the Gherkin block changed.
Workflow
- Identify the Gherkin region: whole
.featurefile, fencedgherkinblock, indented block, quoted acceptance criteria, or inline scenario text. - Preserve the surrounding wrapper unless explicitly asked to change it. For Markdown input, return the heading/prose/fence context, not just the fenced Gherkin block.
- Clarify the behavior as examples: initial state, event, observable outcome.
- Choose the smallest structure that expresses the behavior:
Feature, optionalRule,Background,Scenario/Example, orScenario OutlinewithExamples. - Keep scenarios concrete and short, usually 3-5 steps.
- Review syntax and readability before returning: colons, step keywords, duplicate step text, observable outcomes, and table/doc string formatting.
Quick Reference
| Construct | Use for | Syntax note |
|---|---|---|
Feature: | One high-level capability per feature document or block | Requires : |
Rule: | Group scenarios under one business rule | Requires : |
Scenario: / Example: | One concrete example | Requires : |
Background: | Short shared context for following scenarios | Requires :; one per Feature or Rule |
Scenario Outline: | Same behavior with varied data | Requires Examples: and <parameter> placeholders |
Examples: | Data rows for an outline | Requires : and a table |
Given | Known state or precondition | No : |
When | Event or action | No : |
Then | Observable outcome | No : |
And / But | Continue the previous step type | No : |
* | Bullet-like step list | Use sparingly for list-style setup |
@tag | Group or filter features/scenarios | Place above the item tagged |
# | Line comment | Line comments only; no block comments |
""" | Doc String | Passed as final step argument |
| ` | ` | Data Table |
Show full SKILL.md (299 more words)Show less
Authoring Rules
- Use the language domain experts use. Avoid translating business behavior into UI clicks, HTTP calls, database rows, queues, mocks, or implementation details.
Givenputs the system in a known state. Avoid user interaction inGivensteps.Whendescribes one meaningful event.Thendescribes an outcome visible to a user or external system. Do not assert hidden database state unless that is the actual external contract.- Use
AndandButto improve flow, not to hide new phases of the scenario. - Avoid identical step text under different step keywords; Cucumber ignores
Given/When/Thenwhen matching step definitions. - Use two-space indentation unless preserving existing style.
- Keep
Backgroundshort and vivid. If it grows beyond about four lines, use higher-level steps or split byRule/Feature. - Use
Scenario Outlineonly when examples share the same behavior and differ by data. - Escape
|as\|, newline as\n, and backslash as\\inside Data Table cells.
Example
Markdown wrapper preserved; only the Gherkin block is authored:
## Acceptance Criteria
```gherkin
Feature: Password reset
Rule: Reset links expire after their allowed lifetime
Scenario: Customer resets their password before the link expires
Given Priya has requested a password reset
And the reset link is still valid
When Priya chooses a new password with the reset link
Then she can sign in with the new password
Scenario: Customer uses an expired reset link
Given Priya has requested a password reset
And the reset link has expired
When Priya tries to choose a new password with the reset link
Then she is told the reset link has expired
And her password is unchanged
```Common Mistakes
| Mistake | Fix |
|---|---|
| Complaining about Markdown around a Gherkin block | Preserve the wrapper and work only on the Gherkin section. |
| Returning only a fenced Gherkin block when the input was Markdown | Return the original Markdown wrapper with only the Gherkin content changed. |
Feature Checkout or Scenario: Place order: | Add the missing colon after Feature; remove extra colon from the scenario title. |
Given I click the checkout button | Move interaction to When; describe state in Given. |
Then an order row exists in the database | Prefer an observable result, such as an order confirmation. |
Reusing the same step text for Given and Then | Change the wording so the domain meaning is distinct. |
| Long scripts with many UI actions | Raise the abstraction and keep the scenario to the behavior. |
Large Background sections | Use higher-level context or split scenarios by Rule or Feature. |
© intent-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/gherkin-authoring of intent-driven-dev/intent-driven-template.
Open the folder on GitHubat commit 73f54d5
Compare with similar skills
Gherkin Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gherkin Authoring this skillintent-driven-dev/intent-driven-template | 159 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Fixgenkovich/sdd | 171 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Goosetown Researcher Beadsaaif-goose/goosetown | 154 | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vibe CodingOfficeDev/microsoft-365-agents-toolkit | 781 | — | ~5.5k | Automated safety check: Pass | Custom licence | |
| Intent Driven Developmentaffaan-m/ECC | 274k | 1 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Implement FeatureLog2n-io/Typhon | 250 | — | ~2k | Automated safety check: Pass | Custom licence |
Similar skills
Goosetown Researcher Beads
aaif-goose/goosetown
Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.
Vibe Coding
OfficeDev/microsoft-365-agents-toolkit
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
Intent Driven Development
affaan-m/ECC
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation.
Implement Feature
Log2n-io/Typhon
Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests…
Squid Refactor
iusztinpaul/squid
Plan a refactor as an ordered, commit-grain Tasks Plan with structural acceptance criteria (suite green at every step, no behaviour diff) that /squid-implement-night can execute end-to-end.
More from intent-driven-dev/intent-driven-template
All 10 skills in this repoAcceptance Test Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…
Adversarial Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use adversarial-authoring skill", "model council", "cross-model review", or…
Architectural Decision Records
intent-driven-dev/intent-driven-template
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…
Glossary
intent-driven-dev/intent-driven-template
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Openspec Bulk Apply Change
intent-driven-dev/intent-driven-template
A skill your agent uses when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
Spec As Source
intent-driven-dev/intent-driven-template
A skill your agent uses when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.
Related
Categories
Questions about Gherkin Authoring
What does Gherkin Authoring do?
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…. Gherkin Authoring is an agent skill from intent-driven-dev/intent-driven-template. 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 embedded in Markdown.
When should I use Gherkin Authoring?
Gherkin Authoring fits situations like: improving Gherkin; cucumber scenarios; BDD acceptance criteria; feature examples.
How do I install Gherkin Authoring in Claude Code?
Run `npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a claude-code`. Or copy the skill folder (.agents/skills/gherkin-authoring in intent-driven-dev/intent-driven-template) into .claude/skills/gherkin-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Gherkin Authoring in Codex?
Run `npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a codex`. Or copy the skill folder (.agents/skills/gherkin-authoring in intent-driven-dev/intent-driven-template) into .agents/skills/gherkin-authoring in your project. Codex loads it when a task matches its description.
Can I use Gherkin Authoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intent-driven-dev/intent-driven-template --skill gherkin-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gherkin-authoring, .gemini/skills/gherkin-authoring, .github/skills/gherkin-authoring and .opencode/skills/gherkin-authoring in your project.
What does Gherkin Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Gherkin Authoring is instructions for the agent only.
Does Gherkin Authoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gherkin Authoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gherkin Authoring use?
Gherkin Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gherkin Authoring use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gherkin Authoring?
Skills that share tags, products or a category with Gherkin Authoring: Fix (genkovich/sdd, 171 stars), Goosetown Researcher Beads (aaif-goose/goosetown, 154 stars), Vibe Coding (OfficeDev/microsoft-365-agents-toolkit, 781 stars) and Intent Driven Development (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gherkin Authoring?
intent-driven-dev (a GitHub organization) maintains it in intent-driven-dev/intent-driven-template, which has 159 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 4, 2026.
Source: intent-driven-dev/intent-driven-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.