bdd-scenarios

Name: bdd-scenarios
Availability: InStock
Author: grimblaz

Automate Given/When/Then scenario authoring with ID traceability and CE Gate coverage detection.

3|Updated Dec 7, 2025

Search Tags:#automation #agile #traceability #scenarios #bdd #gherkin #ce gate

Ready to run

npx skills add https://github.com/Grimblaz/agent-orchestra --skill bdd-scenarios-grimblaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bdd-scenarios
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/bdd-scenarios
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill bdd-scenarios-grimblaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates disciplined Given/When/Then scenario authoring with ID traceability for Agent Orchestra, enabling CE Gate coverage checks and per-scenario classification.

Core Features & Use Cases

Structured scenario authoring using S1, S2, ... with clear Title and Type
Declarative-over-Imperative guidance to improve maintainability
Scenario ID lifecycle management and per-scenario CE Gate extraction
Optional Phase 2 Gherkin conversion and framework integration

Quick Start

Define your first scenario under the Scenarios section using the S1 heading and follow the Given/When/Then pattern

Frequently Asked Questions about bdd-scenarios

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

FAQPage Schema

How do I write BDD scenarios with traceable IDs for CE Gate checks?▼

BDD scenarios are authored using Given/When/Then patterns with unique identifiers like S1, S2 to enable CE Gate coverage checks. The skill automates this structured authoring, managing the ID lifecycle and extracting per-scenario evidence for verification.

How do I convert requirements into Gherkin format for Phase 2 automation?▼

Converting requirements into Gherkin format for Phase 2 is handled through the skill's optional Gherkin conversion feature. It transforms existing issue bodies into structured Given/When/Then scenarios while maintaining ID traceability for framework integration.

What is the best way to classify BDD scenarios as automated or manual?▼

Classifying BDD scenarios as automated or manual is accomplished by tagging each structured Given/When/Then scenario with [auto] or [manual]. This classification prepares per-scenario evidence for Code-Conductor rules during the CE Gate phase.

Why use declarative over imperative style when writing Gherkin scenarios?▼

Declarative Gherkin scenarios are preferred over imperative style to improve maintainability of your BDD tests. The skill provides declarative-over-imperative guidance, focusing on behavior outcomes rather than UI interaction steps.

Can I use this BDD scenario authoring tool with Agile workflows without extra dependencies?▼

Yes, the BDD scenario authoring tool works within Agile workflows without requiring extra dependencies. It operates directly on Issue bodies to structure scenarios, manage ID lifecycles, and detect coverage for the Agent Orchestra.

When do I need structured BDD scenarios for the CE Gate?▼

Structured BDD scenarios are needed for the CE Gate during Phase 2 or final verification to satisfy per-scenario runner and Code-Conductor evidence rules. They provide the ID traceability required to validate automation coverage.