agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/bdd-assistant/SKILL.md

bdd

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Reference for Behavior-Driven Development: Gherkin Given-When-Then format and Three Amigos structure. Use when: writing or reviewing .feature scenarios, choosing ubiquitous language, running a discovery conversation about behaviour. Not for: executing the BDD lifecycle or RED/GREEN automation — that moved to the adoption layer (XSPEC-095); turning .feature files into E2E skeletons — use /e2e. Keywords: BDD, Gherkin, Given When Then, feature file, scenario, Three Amigos, 行為驅動開發, 場景, 特性檔.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-for-agents and research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write Gherkin scenarios using ubiquitous language, make them concrete and specific.

    line 46
  2. Distinctive:

    Keep scenarios current, use as shared documentation, review with stakeholders.

    line 52
  3. Very specific:

    After /bdd completes, the AI assistant should suggest:

    line 86

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28): BDD lifecycle orchestration (4-phase cycle, Gherkin scaffolding, RED/GREEN execution) relocated to adoption layer (XSPEC-095, 2026-04-28). This Skill retains: Gherkin format definition, Three Amigos structure, BDD cycle diagram. For enforced lifecycle execution, use your adoption layer's toolchain. -->

BDD Assistant | BDD 助手

⚠️ Status: Reference（參考用，非可執行流程） — BDD 生命週期協調（4 階段循環、Gherkin scaffolding、RED/GREEN 執行）已於 2026-04-28 移至 adoption layer（XSPEC-095）。此處保留 Gherkin 格式定義、Three Amigos 結構、BDD 循環圖供參考。 Lifecycle orchestration has moved to the adoption layer (XSPEC-095); this document is reference-only. For enforced execution, use your adoption layer's toolchain.

Guide through the Behavior-Driven Development (BDD) workflow using Given-When-Then format.

引導行為驅動開發（BDD）流程，使用 Given-When-Then 格式。

BDD Cycle | BDD 循環

DISCOVERY ──► FORMULATION ──► AUTOMATION ──► LIVING DOCS
    ^                                            │
    └────────────────────────────────────────────┘

Workflow | 工作流程

📖 以下為流程的參考結構，非可執行步驟；自動化／強制執行請用 adoption layer 工具鏈（XSPEC-095）。 The steps below are a reference structure, not an executable workflow.

1. DISCOVERY - Explore Behavior | 探索行為

Discuss with stakeholders, identify examples and edge cases, understand the "why".

2. FORMULATION - Write Scenarios | 制定場景

Write Gherkin scenarios using ubiquitous language, make them concrete and specific.

3. AUTOMATION - Implement Tests | 自動化測試

Implement step definitions, write minimal code to pass, follow TDD within automation.

4. LIVING DOCUMENTATION - Maintain | 活文件維護

Keep scenarios current, use as shared documentation, review with stakeholders.

Gherkin Format | Gherkin 格式

Feature: User Login
  As a registered user
  I want to log in to my account
  So that I can access my dashboard

  Scenario: Successful login
    Given I am on the login page
    When I enter valid credentials
    Then I should see my dashboard

Three Amigos | 三劍客會議

RoleFocus角色關注點
BusinessWhat & Why業務什麼和為什麼
DevelopmentHow開發如何實現
TestingWhat if測試假設情況

Usage | 使用方式

/bdd                              - Start interactive BDD session | 啟動互動式 BDD 會話
/bdd "user can reset password"    - BDD for specific feature | 針對特定功能
/bdd login-feature.feature        - Work with existing feature file | 處理現有功能檔案

Next Steps Guidance | 下一步引導

After /bdd completes, the AI assistant should suggest:

BDD 場景已定義。建議下一步 / BDD scenarios defined. Suggested next steps:

  • 執行 /tdd 實作步驟定義 ⭐ Recommended / 推薦 — Implement step definitions
  • 執行 /checkin 品質關卡（若功能完成）— Quality gates (if feature complete)
  • 與利害關係人審查場景確保業務正確性 — Review scenarios with stakeholders

Reference | 參考

  • BDD Workflow Guide — Read it when running discovery, formulation and automation as a cycle.
  • Gherkin Quick Reference Guide — Read it when writing Given/When/Then and you need the exact syntax.
  • Detailed guide: guide.md
  • Core standard: behavior-driven-development.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/bdd

For complete AI agent behavior definition, see the corresponding command file: /bdd

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free