agentleFS
minikinminikin/keeler/skills/gherkin-specs/SKILL.md

gherkin-specs

Skill4 starsChanged 2 months agoMITView on GitHub

How to write good Given/When/Then scenarios for Keeler specs. Use during /keeler:spec when drafting or amending a spec, and during /keeler:review when checking spec conformance — covers scenario granularity, observable-behavior phrasing, and the traps that make specs untestable.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. cedaniel200/atlas-template★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    One behavior per scenario: If a scenario needs "And" more than ~3 times, it's two scenarios.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing Gherkin Scenarios That Gate Real Code

A Keeler spec's scenarios ARE the acceptance criteria — each becomes a test named after it. Write them so that a failing test points at exactly one broken promise.

Rules

  1. Observable behavior only. Then the display form is "80-101" — yes. Then the ranges vector is merged — no: that's implementation, a refactor would break the spec without breaking the user.
  2. One behavior per scenario. If a scenario needs "And" more than ~3 times, it's two scenarios. Error cases always get their own.
  3. Name the concrete values. Given the input "8100-8000" beats Given an invalid range — concrete values become test fixtures verbatim and kill boundary mutants.
  4. Cover the three families: happy path, each edge (boundaries, empty, maximum), each failure mode (with the exact error the user sees).
  5. Failure scenarios name the offending input in the error — that promise ("error names the token") is itself testable behavior.
  6. One property scenario for every law the Implementation Notes list (round-trip, idempotence, shape) — phrased as Given any valid X.

Template

### Scenario: <behavior in one line, will become a test name>

Given <concrete precondition, with real values>
When  <single action>
Then  <observable outcome>
And   <at most a couple more observables>

Smells

  • A scenario no test could fail → not observable, rewrite.
  • Two scenarios that can't both be implemented → the spec contradicts itself; resolve before approval, not in code.
  • A scenario the implementation satisfies "by accident" with no dedicated test → conformance gap; /keeler:review must flag it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.