← ClaudeAtlas

bdd-step-library-curatorlisted

Use when a Cucumber, Behave or Reqnroll project has grown past ~50 step definitions, before writing a step that may already exist, or when new .feature files need a duplicate check. Inventories steps, merges duplicates, publishes a step-library README and a scenario coverage map.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# bdd-step-library-curator ## Overview After 6 months of a BDD project, step definitions proliferate: - Two engineers write `Given a user` and `Given a logged-in user` for the same fixture. - Three slightly-different "I click X" steps (one for buttons, one for links, one for arbitrary elements) - all do the same thing. - A new engineer can't find existing steps and writes a fourth variant. The result: step library bloat → Gherkin features hard to read, step ambiguities, runtime errors, drift. This skill builds a curation workflow. ## When to use - A BDD project's step count exceeds ~50 (proliferation threshold). - A new engineer reports "I couldn't find a step for X." - Quarterly: scheduled step review. - Before adopting BDD across multiple teams (proactively design the step library shape). ## How to use Work through Steps 1-6 below in order: inventory -> detect duplicates -> recommend consolidations -> reorganize and publish the README -> gate new steps pre-merge -> repeat on a cadence. ## Step 1 - Inventory step definitions Extract every declared step pattern across the project. Each runner uses its own annotation syntax (`@Given` in Cucumber-JVM, `@given` in Behave, `[Given]` in Reqnroll / SpecFlow) - the per-runner extraction commands are in [references/step-extraction-and-overlap.md](references/step-extraction-and-overlap.md). The inventory produces a step audit: ``` Total step definitions: 142 Unique patterns: 138 (4 ambiguous duplicates alread