Stats
Actions
Tags
Guides through Acceptance Test-Driven Development workflow for defining and validating user stories using INVEST criteria and Gherkin-style acceptance criteria.
How this skill is triggered — by the user, by Claude, or both
Slash command
/universal-dev-standards:atdd-assistant [feature or spec | 功能或規格][feature or spec | 功能或規格]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
⚠️ Status: Reference（參考用，非可執行流程） — 5 階段 ATDD 生命週期協調（WORKSHOP→DISTILLATION→DEVELOPMENT→DEMO→DONE、INVEST 驗證、AC→Gherkin 轉換、RED/GREEN 執行、PO sign-off gates）已於 2026-04-28 移至 adoption layer（XSPEC-095）。此處保留 INVEST 準則、ATDD 循環圖、Gherkin AC 格式、Three Amigos 結構供參考。 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 Acceptance Test-Driven Development (ATDD) workflow for defining and validating user stories.
引導驗收測試驅動開發（ATDD）流程，用於定義和驗證使用者故事。
WORKSHOP ──► DISTILLATION ──► DEVELOPMENT ──► DEMO ──► DONE
^ │ │
└──────────────────────────────┴──────────────┘
(Refinement needed)
📖 以下為流程的參考結構，非可執行步驟；自動化／強制執行請用 adoption layer 工具鏈（XSPEC-095）。 The steps below are a reference structure, not an executable workflow.
PO presents user story, team asks clarifying questions, define acceptance criteria together.
Convert AC to executable test format, remove ambiguity, get PO sign-off.
Run acceptance tests (should fail initially), use BDD/TDD for implementation, iterate until all pass.
Show passing acceptance tests, demonstrate working functionality, get formal acceptance.
PO accepted, code merged, story closed.
| Criterion | Description | 說明 |
|---|---|---|
| Independent | Can be developed separately | 可獨立開發 |
| Negotiable | Details can be discussed | 可協商細節 |
| Valuable | Delivers business value | 提供商業價值 |
| Estimable | Can estimate effort | 可估算工作量 |
| Small | Fits in one sprint | 一個 Sprint 可完成 |
| Testable | Has clear acceptance criteria | 有明確驗收條件 |
As a [role],
I want [feature],
So that [benefit].
### Acceptance Criteria
- Given [context], when [action], then [result]
/atdd - Start interactive ATDD session | 啟動互動式 ATDD 會話
/atdd "user can reset password" - ATDD for specific feature | 針對特定功能
/atdd US-123 - ATDD for existing user story | 處理現有使用者故事
After /atdd completes, the AI assistant should suggest:
驗收測試已定義。建議下一步 / Acceptance tests defined. Suggested next steps:
- 執行
/sdd建立規格文件 ⭐ Recommended / 推薦 — Create a specification document- 執行
/bdd將 AC 轉為 Gherkin 場景 — Convert AC to Gherkin scenarios- 執行
/tdd直接實作驗收測試 — Implement acceptance tests directly
完整的 AI 行為定義請參閱對應的命令文件：
/atddFor complete AI agent behavior definition, see the corresponding command file:
/atdd
npx claudepluginhub asiaostrich/universal-dev-standards --plugin universal-dev-standardsGuides through Behavior-Driven Development workflow using Given-When-Then format. Covers Gherkin scenario writing, Three Amigos meetings, and the BDD cycle.
Guides BDD collaboration with Three Amigos sessions, example mapping, discovery workshops, ubiquitous language, and Gherkin living documentation for devs, testers, stakeholders.