Write Acceptance Test-Driven Development specifications before implementation.
From bmad-coworknpx claudepluginhub bspann/bmad-cowork --plugin bmad-coworkThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Use when writing Acceptance Test-Driven Development specifications before implementation. Run per story when helpful in Phase 4.
Trigger with: "ATDD", "acceptance tests first", "write acceptance tests", "BDD specs"
Agent: TEA (Murat) Input: Story file with acceptance criteria Output: Executable acceptance test specifications
Read the story file. Extract all acceptance criteria (Given/When/Then).
For each criterion, expand into detailed test scenarios:
Create test files that express the acceptance criteria as executable tests. Tests should:
Present the expanded test scenarios. Confirm they accurately capture the intended behavior.
Save test spec files alongside the story. These become the contract that dev-story must satisfy.