skills.rest
SmidigStorm
SmidigStormCOMMUNITY
Explore all skills by this author →
GitHub

requirements-writing

Generate Gherkin Given-When-Then scenarios and feature files for BDD.

Updated Jan 12, 2026
Search Tags:#bdd#gherkin#clarifying-questions#requirements-writing#scenario-generation#no-assumptions
One-click install
npx skills add https://github.com/SmidigStorm/bdd-ai-showcase --skill requirements-writing-smidigstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-writing
Source: https://github.com/SmidigStorm/bdd-ai-showcase/tree/main/.claude-code/pm-requirements/skills/requirements-writing
Command: npx skills add https://github.com/SmidigStorm/bdd-ai-showcase --skill requirements-writing-smidigstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams write clear, Gherkin-based requirements for Behavior-Driven Development. It prevents ambiguity by enforcing a no-assumptions policy and guides you to structure features with Given-When-Then scenarios.

Core Features & Use Cases

  • No assumptions policy enforcement: prompts clarifying questions when information is missing.
  • Guided Gherkin structure: ensures one behavior per scenario and proper use of Feature, Rule, Scenario, Given/When/Then.
  • Automatic scenario generation: creates well-formed feature files with proper tags and organization by Rule.
  • Documentation of gaps: records open questions directly in the feature file when information is unknown.

Quick Start

Generate a feature file for a new user login flow with a single behavior per scenario and placeholders for domain-specific questions.

Frequently Asked Questions about requirements-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Gherkin scenarios for behavior-driven development?▼

This skill generates BDD Gherkin scenarios by applying a no-assumptions policy, prompting clarifying questions for missing information, and documenting open questions directly within the feature file.

How do I generate a complete Gherkin feature file from a user story?▼

The skill generates complete Gherkin feature files from user stories by creating well-formed scenarios with proper tags, organizing them by Rule, and validating the Gherkin structure.

What is the best way to handle missing information when writing BDD requirements?▼

Handling missing information in BDD requirements involves enforcing a no-assumptions policy; this skill prompts clarifying questions and records open questions directly in the feature file.

Can I use this to validate Gherkin structure and ensure one behavior per scenario?▼

Yes, this validates Gherkin structure by ensuring one behavior per scenario and guiding proper use of Feature, Rule, Scenario, and Given/When/Then keywords.

Why does my BDD feature file contain open questions instead of test steps?▼

BDD feature files contain open questions because the no-assumptions policy documents gaps directly in the file when information is unknown, rather than generating incorrect test steps.

Related Skills

Explore More Content & Communication Skills→
Adelie-SquadAdelie-Squad
17

jobs-stories

Generate Job Stories, User Stories, and Gherkin acceptance criteria from product briefs.

Official
Advanced
pantheon-orgpantheon-org
9

bdd-testing

Create and run Cucumber BDD tests using Gherkin syntax and feature files.

Official
Advanced
luokai25luokai25

oc-agile-toolkit

Provide expert Agile coaching for Scrum, Kanban, SAFe, and Management 3.0 questions.

Community
Advanced
vincehvinceh
1

acceptance-test-writing

Generate acceptance criteria and Gherkin Given-When-Then scenarios for user stories.

Community
Advanced