atdd

SkillDev tools

[UDS] Reference for Acceptance Test-Driven Development: INVEST criteria, Gherkin AC format, and Three Amigos structure. Use when: defining acceptance criteria with a product owner, running a specification workshop, checking a user story against INVEST. Not for: executing the ATDD lifecycle or enforcing PO sign-off gates — that moved to the adoption layer (XSPEC-095); writing unit tests — use /tdd. Keywords: ATDD, acceptance test, acceptance criteria, INVEST, specification workshop, Three Amigos, 驗收測試驅動開發, 驗收條件, 規格工作坊.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the atdd skill

What this skill tells your AI

The instructions your AI receives, as published by asiaostrich/universal-dev-standards in skills/atdd-assistant/SKILL.md and read by ahel’s review.

ATDD Assistant | ATDD 助手

⚠️ 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)流程,用於定義和驗證使用者故事。

ATDD Cycle | ATDD 循環

WORKSHOP ──► DISTILLATION ──► DEVELOPMENT ──► DEMO ──► DONE
    ^                              │              │
    └──────────────────────────────┴──────────────┘
                  (Refinement needed)

Workflow | 工作流程

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

1. WORKSHOP - Define AC | 定義驗收條件

PO presents user story, team asks clarifying questions, define acceptance criteria together.

2. DISTILLATION - Convert to Tests | 轉換為測試

Convert AC to executable test format, remove ambiguity, get PO sign-off.

3. DEVELOPMENT - Implement | 實作

Run acceptance tests (should fail initially), use BDD/TDD for implementation, iterate until all pass.

4. DEMO - Present | 向利害關係人展示

Show passing acceptance tests, demonstrate working functionality, get formal acceptance.

5. DONE - Complete | 完成

PO accepted, code merged, story closed.

INVEST Criteria | INVEST 準則

CriterionDescription說明
IndependentCan be developed separately可獨立開發
NegotiableDetails can be discussed可協商細節
ValuableDelivers business value提供商業價值
EstimableCan estimate effort可估算工作量
SmallFits in one sprint一個 Sprint 可完成
TestableHas clear acceptance criteria有明確驗收條件

User Story Format | 使用者故事格式

As a [role],
I want [feature],
So that [benefit].

### Acceptance Criteria
- Given [context], when [action], then [result]

Usage | 使用方式

/atdd                              - Start interactive ATDD session | 啟動互動式 ATDD 會話
/atdd "user can reset password"    - ATDD for specific feature | 針對特定功能
/atdd US-123                       - ATDD for existing user story | 處理現有使用者故事

Next Steps Guidance | 下一步引導

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

Reference | 參考

AI Agent Behavior | AI 代理行為

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

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

Signals

GitHub stars
73
Forks
13
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
atdd
Source
github.com/asiaostrich/universal-dev-standards