Generate Gherkin feature files and step definition stubs from issues.
npx skills add https://github.com/ubiquitousthey/exo --skill bdd-author
Please help me install this Agent Skill. Skill: bdd-author Source: https://github.com/ubiquitousthey/exo/tree/main/skills/bdd-author Command: npx skills add https://github.com/ubiquitousthey/exo --skill bdd-author
This skill removes the manual, error-prone work of turning issue requirements into executable BDD feature files and corresponding step definitions, ensuring tests are traceable to requirements and issues.
Run the bdd-author write action with an issue title and body to create a Gherkin feature file, then run bdd-author automate for that feature file to scaffold step definitions.
High-intent search queries and answers about installing and using this skill.
You can generate Gherkin feature files from GitHub issues by parsing the issue title and body to create scenarios with traceability tags like @REQ-XXX and @issue-N, ensuring tests remain traceable to original requirements. This automates converting acceptance criteria into executable feature files.
Yes, you can scaffold BDD step definitions across Python, JavaScript/TypeScript, Ruby, Go, and JVM languages by detecting framework conventions and generating unique Given/When/Then step stubs with TODOs, avoiding duplicate definitions across the project's test directory.
Traceability tagging preserves @REQ-XXX, @issue-N, and @AC-N tags within generated Gherkin feature files to maintain a direct link between acceptance criteria in issues and the executed test scenarios, ensuring full requirements coverage visibility throughout the test automation lifecycle.
The best way to avoid duplicate step definitions in BDD test automation is to extract unique Given/When/Then steps from existing feature files and check against current project definitions before generating framework-appropriate stubs, ensuring no redundant test code is introduced.
Framework detection scans the software repository to identify the active BDD framework and locate the appropriate test directory, inferring conventions from dependencies and file structures to place generated step definitions and feature files correctly within the project.
If your project is missing BDD framework dependencies, the system reports the absent packages and provides specific installation guidance, ensuring the generated step definitions and feature files can execute immediately within the detected language environment without manual troubleshooting.
synaptiaiCreate convention-compliant branches and tasks from repository issues with dependencies.
cuongtl1992Analyze Playwright-BDD/Cucumber feature files and step definitions for quality issues.
pantheon-orgCreate and run Cucumber BDD tests using Gherkin syntax and feature files.
rysweetWrite and refine Gherkin feature files and step definitions for BDD best practices.
