discovery

Guide interactive BDD discovery sessions and generate Gherkin .feature files.

Updated Jan 18, 2026

Search Tags:#documentation #specification #bdd #gherkin #behavior driven development #feature files

Ready to run

npx skills add https://github.com/fahchen/skills --skill discovery-fahchen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/fahchen/skills/tree/main/plugins/bdd/skills/discovery
Command: npx skills add https://github.com/fahchen/skills --skill discovery-fahchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining and documenting software behavior using Behavior-Driven Development (BDD) patterns, ensuring clarity and alignment between stakeholders and development teams.

Core Features & Use Cases

Interactive Discovery: Guides users through defining features, rules, and examples.
Automated Output Generation: Creates Gherkin .feature files and Behavior Decision Records (BDRs).
Glossary Management: Helps maintain a shared understanding of domain terminology.
Use Case: A product manager and a developer can use this Skill to collaboratively define the acceptance criteria for a new user authentication feature, resulting in a clear .feature file ready for implementation.

Quick Start

Use the discovery skill to start defining a new feature for user login.

Frequently Asked Questions about discovery

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

FAQPage Schema

How do I define software behavior using Gherkin feature files?▼

You can define software behavior by running interactive discovery sessions that guide you through specifying features, business rules, and concrete examples to generate Gherkin .feature files.

What is behavior driven development and when do I need a BDD discovery session?▼

Behavior Driven Development (BDD) requires a shared understanding between stakeholders and developers. You need a discovery session to collaboratively define acceptance criteria and document feature behavior.

How do I create Gherkin feature files from business rules and concrete examples?▼

To create Gherkin feature files, an interactive discovery process guides you through defining business rules and examples, automatically generating the .feature files ready for implementation.

Can I maintain a shared domain glossary and detect conflicts in BDD specifications?▼

Yes, you can maintain a shared domain glossary and detect specification conflicts within the spec/ directory structure during the discovery process to ensure consistent terminology.

What is the best way to document acceptance criteria for developers and product managers?▼

The best way to document acceptance criteria collaboratively is by generating Behavior Decision Records (BDRs) and Gherkin .feature files that clearly specify software features and rules.

What are the limitations of using discovery sessions for BDD specification?▼

Discovery sessions rely on interactive user guidance and a structured spec/ directory, meaning they require active stakeholder participation to define features and cannot generate specifications autonomously.