doc-bdd

仓库创建 2025年11月10日最近提交 25 天前SkillHot 收录 25 天前

这个 Skill 做什么

把 EARS 那类形式化需求翻译成可执行的 BDD 场景，产出 YAML 格式的 Given/When/Then 用例，并在每个场景上保留需求到 SPEC 的 trace 链接。在完成 EARS 分析、准备写 ADR 或实现前用它来生成验收测试用例。它的亮点是把需求元素逐条关联到规范，便于自动化执行和追踪覆盖范围。

▸ 展开 SKILL.md 英文原文

Create Behavior-Driven Development (BDD) scenarios - Layer 4 of the SDD flow, translating EARS requirements into executable Given-When-Then acceptance scenarios with req-to-SPEC trace links. Use after EARS, before ADR.

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/main/platforms/claude-code-plugin/skills/doc-bdd/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/main/platforms/claude-code-plugin/skills/doc-bdd/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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. (An optional
on-demand emitter, `tools/bdd_to_gherkin.py`, generates `.feature` files from the
YAML if a runner ever needs them.)

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

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有