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

atdd

Skill4 starsChanged 29 days agoMITView on GitHub

[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, 驗收測試驅動開發, 驗收條件, 規格工作坊.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    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:

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

    line 51
  2. Very specific:

    After /atdd completes, the AI assistant should suggest:

    line 91

“Common” is measured: kept by at least 6 in 10 of the 4 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): ATDD lifecycle orchestration (5-phase: WORKSHOP→DISTILLATION→DEVELOPMENT→DEMO→DONE, INVEST validation, AC→Gherkin conversion, RED/GREEN execution, PO sign-off gates) relocated to adoption layer (XSPEC-095, 2026-04-28). This Skill retains: INVEST criteria table, ATDD cycle diagram, Gherkin AC format, Three Amigos structure. For enforced lifecycle execution, use your adoption layer's toolchain. -->

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 | 參考

  • Acceptance Criteria Writing Guide — Read it when writing or reviewing acceptance criteria.
  • ATDD Workflow Guide — Read it when running the ATDD cycle end to end.
  • Detailed guide: guide.md
  • Core standard: acceptance-test-driven-development.md

AI Agent Behavior | AI 代理行為

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

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

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