Transform multi-file requirements into structured Gherkin Given/When/Then specifications.
npx skills add https://github.com/Ting-s515/skills --skill export-gherkin
Please help me install this Agent Skill. Skill: export-gherkin Source: https://github.com/Ting-s515/skills/tree/main/export-gherkin Command: npx skills add https://github.com/Ting-s515/skills --skill export-gherkin
此技能可以將分散的需求內容轉換為 Gherkin（Given/When/Then）格式，協助團隊以清晰的規格對齊驗收標準，減少溝通成本。
將待轉換的需求檔案放入工作區並呼叫此技能以產生對應的 Gherkin 規格。
High-intent search queries and answers about installing and using this skill.
To convert requirements into Gherkin scenarios, provide your requirement documents in the workspace and invoke the Skill to transform disparate inputs into a structured Feature/Scenario format using Given/When/Then keywords.
Generating Gherkin specifications from multiple documents involves placing all scattered files into the workspace to output a consistent Feature/Scenario format, standardizing acceptance testing criteria for better tracking.
Yes, you can align PM, QA, and developers by converting requirement documents into clear Gherkin specifications, reducing communication costs by providing a shared Given/When/Then structure for acceptance testing.
Yes, this Skill supports multi-file input for requirements gathering. Place multiple disparate requirement files into the workspace, and it will process them to output a unified Gherkin specification format.
You need to export Gherkin specifications for design reviews when you have scattered requirements that require a consistent Given/When/Then structure, ensuring testing and verification alignment across multi-file documents.
wangc94Convert URLs, PDFs, Word, Markdown, and text into structured multi-section briefings.
hmctsConverts acceptance criteria into Cucumber/Gherkin feature files with backgrounds and tags.
andresdiegolandaGenerate user stories with acceptance criteria from design artifacts.
iCesofTApply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.
