A tool for writing Behavior-Driven Development (BDD) acceptance scenarios from EARS requirements. BDD scenarios describe the starting situation, the action, and the expected result in structured YAML, with links back to requirements and forward to design sections.

Use it after EARS requirements exist to create acceptance scenarios before architecture and detailed specifications are written.

It turns formal requirements into concrete examples that can be checked by people and later mapped to tests. BDD here is used for QA staging, while ordinary tests are used in continuous integration.

doc-bdd — Skill for Claude Code by vladm3105

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add vladm3105/aidoc-flow-framework

Claude Code

/plugin install aidoc-flow

Made for: Claude Code.

Or install aidoc-flow, the plugin that ships this one along with the rest of its 52 skills, 12 commands, 11 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-bdd.svg)](https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-bdd)

Your own site

<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-bdd"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-bdd.svg" alt="Measured on agentmods" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,009 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.03009
Opus 5	$0.00040	$0.01504
Sonnet 5	$0.00016	$0.00602
Haiku 4.5	$0.00008	$0.00301

Measured yesterday against content hash 1345bea1733f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

doc-bdd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

platforms/claude-code-plugin/skills/doc-bdd/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

doc-bdd

Purpose

Create Behavior-Driven Development (BDD) scenarios — Layer 4 of the SDD flow. A BDD suite translates EARS formal requirements into structured YAML scenarios (Given/When/Then phase lists carried in a ```yaml block, NOT Gherkin @-tags), each carrying an element-level ears: trace list and a spec_trace link forward to the SPEC sections it exercises. (If a runner ever needs .feature files, the YAML is the source of record and a .feature emitter can be authored on demand — no such emitter ships today; the only shipped transcoder is the one-off reverse-direction tools/gherkin_to_bdd_yaml.py used to migrate legacy Gherkin into the YAML form.)

Layer: 4. Upstream: EARS (per the necessary-upstream contract; upstream PRD/BRD lineage is reachable transitively via the @-tag chain). Downstream: ADR → SPEC → TDD → IPLAN → Code.

BDD scenarios are the acceptance source of truth that TDD (Layer 7) maps to concrete test cases. Execution is QA-staging only — never run BDD in CI (use TDD unit/integration tests for CI).

When to Use

Use doc-bdd when:

EARS (Layer 3) exists and you need executable acceptance scenarios.
Validating EARS requirements with concrete Given-When-Then behaviors.
Defining the req-to-SPEC trace bridge (spec_trace) before ADR/SPEC.

For end-to-end generation from EARS, a prompt, or an IPLAN, use ../doc-bdd-autopilot/SKILL.md. Create upstream artifacts first; never invent placeholders like EARS-XXX or reference documents that do not yet exist.

Prerequisites

BDD is Layer 4, so the required upstream EARS must already exist. Confirm it and read the spec before writing:

Template (source of truth): ${CLAUDE_PLUGIN_ROOT}/framework/layers/04_BDD/BDD-TEMPLATE.yaml
Layer README: ${CLAUDE_PLUGIN_ROOT}/framework/layers/04_BDD/README.md
ID & tag standards: ${CLAUDE_PLUGIN_ROOT}/framework/governance/ID_NAMING_STANDARDS.md
Authoring style: ${CLAUDE_PLUGIN_ROOT}/framework/governance/AUTHORING_STYLE.md

Read the full file on GitHub · 215 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday Changed 1345bea1733f
2d ago Changed fb6b05d9c907
6d ago First seen · 215 lines · 80 tokens per session scan A 4e81b75ed83f

Subscribe to this mod's changes

doc-bdd is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 3,009 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

doc-bdd

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

doc-bdd

Purpose

When to Use

Prerequisites

What this file has done since we first saw it

Other skills, from other repositories

research-engineer

tika-eval-compare

neuron-evaluation-engineer

jetson-validate-image

atmos-validation

skill-benchmark