Write Gherkin feature specifications into .feature files for BDD workflows.
npx skills add https://github.com/0xdeafcafe/skills --skill write-spec-0xdeafcafe
Please help me install this Agent Skill. Skill: write-spec Source: https://github.com/0xdeafcafe/skills/tree/main/skills/write-spec Command: npx skills add https://github.com/0xdeafcafe/skills --skill write-spec-0xdeafcafe
This Skill helps you create clear, testable Gherkin feature specifications without guessing the repository's conventions or missing important scenarios. It reduces the risk of vague, incomplete, or misleading specs by guiding you through the right questions before writing the .feature file.
Ask the write-spec skill to draft a Gherkin feature file for the behavior you want to capture and be ready to answer a few questions about the main flow, edge cases, and expected outcomes.
High-intent search queries and answers about installing and using this skill.
Writing Gherkin feature specifications involves interactively extracting the golden path and edge cases from loose requests, then generating a concrete .feature file that matches your repository's existing naming and phrasing conventions.
The best way to match repository conventions is to use a spec-writing process that discovers existing spec folders, ADR context, and tagging patterns, ensuring new Gherkin feature files align with local Cucumber or Behave practices.
Yes, this Gherkin spec-writing approach works with pytest-bdd, SpecFlow, Behave, and Cucumber workflows, applying consistent BDD scenario discovery and optional dry-run syntax verification across these BDD runners.
You discover edge cases and error paths in BDD specs through an interactive scenario discovery process that asks targeted questions to draw out scope boundaries and expected outcomes before drafting the final Gherkin file.
Yes, you can validate Gherkin syntax with a dry run when a BDD runner is available, verifying the generated .feature file syntax after writing the behavior specifications and encouraging a final review.
You should link ADRs to a new feature spec when prior design decisions impact the current behavior, allowing the spec-writing process to look up related ADR context and connect the Gherkin scenarios to relevant architectural choices.
Ab0umarValidate Git branch names against feature-branch naming rules.
wuzinongTransform user stories and acceptance criteria into executable Gherkin BDD scenarios.
MathiasPaulenkoIntegrate Gherkin feature files with Python step definitions using behave.
IntegralistGenerate Gherkin specifications from feature descriptions for BDD testing.
