Learn what defines effective BDD scenarios SKILL.md skillA

Learn what defines effective BDD scenarios from intai/story-flow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add intai/story-flow/Learn what defines effective BDD scenarios@git:20260813.f0239bc

Pins git:20260813.f0239bc in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
intai/story-flow
Path
plugins/junior-flow/skills/learn-bdd-scenarios/SKILL.md
Versions recorded
5
Latest version
git:20260813.f0239bc, committed Aug 13, 2026
First version recorded
Feb 2, 2026
Size
8,713 bytes
Repository stars
16
License
MIT

Interactive guidance on writing complete, effective BDD scenarios for story-flow.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# What Defines Effective, Complete BDD Scenarios

## Overview

This learning module helps junior developers understand how to write BDD (Behavior-Driven Development) scenarios that are effective for story-flow's automated testing workflow.

## Instructions

Present the following content interactively. After each section, use `AskUserQuestion` to offer 3 options:
- "Continue to next section"
- "Show more examples"
- "I have a question"

---

## Section 1: The Purpose of BDD Scenarios

Explain that in story-flow, BDD scenarios serve two purposes:

1. **Executable specifications** - Claude uses Playwright MCP to execute these scenarios directly in a browser
2. **Regression test generation** - With `--record` flag, scenarios become Playwright `.spec.js` files

This means scenarios must be:
- **Precise enough** for automated execution
- **Complete enough** to verify the feature works correctly
- **Structured correctly** so Claude can follow them step-by-step

---

## Section 2: Anatomy of an Effective BDD Scenario

Present this structure with explanations:

```gherkin
Feature: [Feature name matching the story]

Background:
  # Shared setup steps that run before EVERY scenario
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add intai/story-flow/Learn what defines effective BDD scenarios@sha256:398da2361727bd14

The line at the top of this page pins the label git:20260813.f0239bc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_pufqp2b5ztk7pdle.svg)](https://markdownregistry.com/a/art_pufqp2b5ztk7pdle)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Feb 2, 2026 and Aug 13, 2026, about one every 48 days.

versioncommittedcommitsizeaudit
git:20260813.f0239bc latest2026-08-13 f0239bc 8,713 BA view · diff
git:20260730.a9a89ce2026-07-30 a9a89ce 8,650 BA view · diff
git:20260729.fcd7bc52026-07-29 fcd7bc5 8,308 BA view · diff
git:20260216.ed289a52026-02-16 ed289a5 8,297 BA view · diff
git:20260202.7a9fda92026-02-02 7a9fda9 8,275 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (8713 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

intai/story-flow · 16 stars · license MIT · pushed 2026-11-04 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_pufqp2b5ztk7pdle
GET https://markdownregistry.com/api/v1/resolve?ref=intai/story-flow/Learn what defines effective BDD scenarios
GET https://markdownregistry.com/api/v1/blob/398da2361727bd1417aaea6982cbc217c1e5874576657ff7e65328429614c9a9

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from intai/story-flow

Learn why to review implementation even with 100% test coverage SKILL.md skill
intai/story-flow · plugins/junior-flow/skills/learn-review-implementation/SKILL.md · Interactive guidance on why human code review is essential for readability and maintainability.
git:20260216.ed289a5 · audit A · 16 stars
Learn why to discuss technical design before implementation SKILL.md skill
intai/story-flow · plugins/junior-flow/skills/learn-technical-design/SKILL.md · Interactive guidance on creating technical design PRs to align with your team before coding.
git:20260811.7c0af34 · audit A · 16 stars
Analyze task dependencies for parallel execution SKILL.md skill
intai/story-flow · plugins/story-flow/skills/analyze-task-dependencies/SKILL.md · Parse story markdown to identify task dependencies and parallel execution opportunities.
git:20260910.adf7c27 · audit A · 16 stars
Draft a story markdown from a story tracker or feature description SKILL.md skill
intai/story-flow · plugins/story-flow/skills/draft-story-markdown/SKILL.md · Generate a draft story markdown by analyzing a story tracker or feature description, Figma designs, and the codebase.
git:20261014.3af5928 · audit A · 16 stars
Execute BDD scenarios SKILL.md skill
intai/story-flow · plugins/story-flow/skills/execute-bdd-scenario/SKILL.md · Execute BDD test scenarios from .feature files using browser automation.
git:20261104.ffce5b2 · audit A · 16 stars
Implement a story according to the requirements and tasks SKILL.md skill
intai/story-flow · plugins/story-flow/skills/implement-story-markdown/SKILL.md · Implement story.md requirements and tasks.
git:20261003.f640913 · audit A · 16 stars
Plan BDD scenarios SKILL.md skill
intai/story-flow · plugins/story-flow/skills/plan-bdd-scenarios/SKILL.md · Plan BDD scenarios.
git:20261016.7c93170 · audit A · 16 stars
Prepare implementation review comments on a pull request SKILL.md skill
intai/story-flow · plugins/story-flow/skills/prepare-implementation-review-comments/SKILL.md · Post reviewer-facing evidence on a pull request - reading order, requirement traceability, risks, discussion points…
git:20261029.3a24c1b · audit A · 16 stars
Review a story markdown against a story tracker SKILL.md skill
intai/story-flow · plugins/story-flow/skills/review-story-against-ticket/SKILL.md · Review story.md requirements and tasks, optionally against a story from the story tracker.
git:20261002.c0ba224 · audit A · 16 stars

Every file in intai/story-flow

Browse by kind, by grade A, or by owner.