Loading...
Loading...
Found 33 Skills
Core Cucumber concepts, Gherkin syntax, and feature file structure
Transform user stories and specifications into precise, verifiable Gherkin acceptance criteria using Given/When/Then syntax with Happy Path, Sad Path, and edge case scenarios. Use when asking for acceptance criteria, Gherkin scenarios, BDD criteria, test scenarios, or AC generation.
Automated BDD scenario generation from EARS requirements - generates Gherkin Given-When-Then scenarios with ADR-Ready scoring
Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration
Validate Behavior-Driven Development (BDD) documents against Layer 4 schema standards
[UDS] Guide through Behavior-Driven Development workflow
This skill should be used when a designer is picking up a Task issue to add design coverage. Triggers on phrases like "I want to design task
Cucumber best practices, patterns, and anti-patterns
This skill should be used when a developer or QA engineer wants to report a bug, create a bug ticket, document a test failure, log a defect, file an issue found during a QA session, or report something that is broken — for example "report a bug", "create a bug ticket", "I found a defect", "something is broken in task