skills.rest
hiiamsky
hiiamskyCOMMUNITY
Explore all skills by this author →
GitHub

bdd-conventions

Standardize Story and Scenario formatting with SC-XX-YY numbering and contract rules.

Updated Apr 4, 2026
Search Tags:#e2e#specifications#bdd#contracts#sc-xx-yy#qa-qc
One-click install
npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill bdd-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bdd-conventions
Source: https://github.com/hiiamsky/multi-agent-dev-team/tree/main/.github/skills/bdd-conventions
Command: npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill bdd-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BDD conventions ensure all three agents (SA/SD, E2E, QA/QC) speak the same language when crafting and validating behavior-driven requirements. By enforcing a single format for Story and Scenario definitions, SC-XX-YY numbering, and contract derivations, teams avoid misinterpretations and drift.

Core Features & Use Cases

  • Unified Story and Scenario structure for cross-team alignment
  • SC-XX-YY numbering scheme with clear traceability
  • Frozen Contract declarations and API contract derivation rules for consistent interface expectations

Quick Start

Create a BDD blueprint file following the defined Story and Scenario format and ensure SC-XX-YY numbering for all stories and scenarios.

Frequently Asked Questions about bdd-conventions

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

FAQPage Schema
How do I standardize BDD scenarios across multiple teams?▼

To standardize BDD scenarios across SA/SD, E2E, and QA/QC, use a unified Story and Scenario structure with SC-XX-YY numbering to ensure consistent definitions and traceability across agents.

What is a Frozen Contract declaration in BDD specifications?▼

A Frozen Contract declaration in BDD specifications defines API contract derivation rules to maintain a single source of truth for interface expectations across SA/SD writers and E2E tests.

How do I map E2E tests to BDD stories and scenarios?▼

You map E2E tests to BDD stories and scenarios by applying SC-XX-YY numbering and Frozen Contract declarations, ensuring E2E test mapping aligns directly with the unified Story and Scenario format.

How does QA validate full scenario coverage for BDD requirements?▼

QA validates full scenario coverage for BDD requirements by enforcing the single source of truth provided by the standardized Story and Scenario structure and the SC-XX-YY numbering scheme.

When do I need SC-XX-YY numbering for behavior-driven development?▼

You need SC-XX-YY numbering for behavior-driven development when cross-team alignment is required, as it provides clear traceability for all stories and scenarios across SA/SD, E2E, and QA/QC agents.

Does standardizing BDD conventions prevent drift between agents?▼

Standardizing BDD conventions prevents drift between agents by ensuring SA/SD, E2E, and QA/QC speak the same language, enforcing a single format for Story and Scenario definitions and contract derivations.

Related Skills

Explore More Software Engineering Skills→
dev-goraebapdev-goraebap

requirements-analyzer

Extracts minimum viable information from requirements documents to bootstrap an FSD blueprint.

Community
Intermediate
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
RDEWAIRDEWAI
5

update-pipeline

Modify CI/CD pipeline configurations incrementally while preserving existing deployment workflows.

Official
Advanced
hmctshmcts
3

generate-bdd-specs

Converts acceptance criteria into Cucumber/Gherkin feature files with backgrounds and tags.

Official
Intermediate