gherkin-expert
Gherkin/BDD specification expert for writing behavioral scenarios, acceptance criteria, and applying structured specifications to improve code generation quality
What this skill does
# Gherkin Expert Skill ## Purpose Provides expert-level Gherkin/BDD specification assistance for writing behavioral scenarios that clarify acceptance criteria and improve downstream code generation quality. ## When This Skill Activates - User asks to write or review Gherkin feature files or scenarios - User needs help structuring complex acceptance criteria - User wants to translate business requirements into Given/When/Then format - User asks about BDD methodology or scenario design - User wants behavioral specifications for multi-actor or multi-step workflows - User mentions Cucumber, SpecFlow, or BDD frameworks - User is working on features with complex acceptance criteria that would benefit from structured scenarios ## How It Works This skill delegates to the `gherkin-expert` agent which has knowledge of: 1. **Gherkin syntax and idioms** — Feature/Scenario/Given/When/Then, backgrounds, scenario outlines, data tables, tags 2. **BDD methodology** — discovery workshops, living documentation, specification by example 3. **Scenario design** — single-behavior focus, declarative style, avoiding implementation details 4. **Domain modeling** — ubiquitous language, bounded contexts expressed through scenarios 5. **AI prompt improvement** — using Gherkin specs as prompt context for better code generation (empirically validated: +26% over English-only) ## When Gherkin Adds Value (Judgment Call) Gherkin is a tool, not a rule. Use judgment: **Good fit:** - Complex multi-step behavioral requirements with many edge cases - Multi-actor scenarios (user does X, system responds Y, admin sees Z) - Business rules with combinatorial conditions (scenario outlines) - Acceptance criteria that stakeholders need to validate - Features where "what done looks like" is ambiguous in English **English is fine:** - Simple CRUD operations with obvious behavior - Internal tooling with a single developer as audience - Config changes, styling, documentation - Requirements where the hard part is algorithm design, not behavior specification ## Usage Examples ``` # Write scenarios for a feature /gherkin-expert Write Gherkin scenarios for our user authentication flow # Review existing scenarios /gherkin-expert Review these acceptance criteria for completeness # Translate requirements to BDD /gherkin-expert Convert these business rules into Given/When/Then scenarios # Decide if Gherkin is appropriate /gherkin-expert Should I write Gherkin scenarios for this retry cascade feature? # Improve scenarios /gherkin-expert These scenarios feel too implementation-focused, help me make them declarative ``` ## Key Resources - Gherkin experiment results: `experiments/hive_mind/gherkin_v2_recipe_executor/` - Issue #3939: Formal specification integration roadmap - Gherkin reference: https://cucumber.io/docs/gherkin/reference/
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.