nw-bdd-requirements

Facilitate BDD requirements discovery using Example Mapping and Three Amigos sessions.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-bdd-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-bdd-requirements
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-bdd-requirements
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-bdd-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BDD collaboration often struggles with misalignment; this skill provides methodology (Example Mapping, Three Amigos, conversational patterns) to discover requirements effectively.

Core Features & Use Cases

  • Three Amigos, Example Mapping, conversational patterns, Given-When-Then translation, and collaborative specification
  • Guidance for translating scenarios into Gherkin-like structures, capturing acceptance criteria, and maintaining ubiquitous language
  • Use cases include team alignment, boundary exploration, red card management, and bridging business and technical perspectives

Quick Start

Use the skill to facilitate a discovery workshop and translate user stories into concrete examples and acceptance criteria.

Frequently Asked Questions about nw-bdd-requirements

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

FAQPage Schema
How do I facilitate a Three Amigos session for BDD requirements discovery?

Use Example Mapping to break down user stories into concrete examples, rules, and acceptance criteria during Agile story refinement. This collaborative method captures ubiquitous language and translates scenarios into Given-When-Then structures.

How do I translate user stories into Given-When-Then acceptance criteria?

Use Example Mapping to break down user stories into concrete examples, rules, and acceptance criteria during Agile story refinement. This collaborative method captures ubiquitous language and translates scenarios into Given-When-Then structures.

What is the best way to align business and technical language during story refinement?

Align business and technical language by maintaining a ubiquitous language throughout collaborative BDD discovery and conversational patterns. This ensures shared understanding and reduces misalignment between stakeholders during requirement elicitation.

Can I use Example Mapping for boundary exploration and red card management?

Use Example Mapping for boundary exploration and red card management to identify edge cases and constraints during requirement discovery. This technique helps agile teams document acceptance criteria and capture assumptions visually.

Does this approach support generating Gherkin-like structures from collaborative specifications?

This approach supports translating collaborative specifications into Gherkin-like structures by deriving Given-When-Then scenarios from mapped examples. It provides methodology to document acceptance criteria effectively for software projects.