implement

Test-driven development automates feature implementation by writing failing tests first, then implementing code to pass them, and refactoring while keeping tests green. This Skill applies the RED-GREEN-REFACTOR cycle to task specifications, loading workspace task markdowns and using bmad-commands to perform deterministic file and test operations with 80% test coverage verification.

Yes. Automated acceptance verification validates that all acceptance criteria are met via automated checks. This Skill loads task specs, executes the TDD cycle, verifies test coverage against an 80% threshold, ensures no syntax errors, and reports completion telemetry to confirm acceptance criteria are satisfied.

This Skill loads task specifications from `workspace/tasks/{task_id}.md` files and applies deterministic file and test operations via bmad-commands in development and CI environments. Provide a task identifier (e.g., `task-auth-002-signup`) to load the spec, execute the TDD cycle, and generate results.

Deterministic operations ensure reproducible, repeatable execution of file modifications and test runs across development and continuous integration environments. This Skill uses bmad-commands to guarantee consistent file and test operations, preventing environment-dependent failures and enabling reliable automated acceptance verification.

No. Test-driven development starts by writing failing tests before implementing code. This Skill enforces the RED-GREEN-REFACTOR workflow, where you write tests first for new features, then implement code to pass them, ensuring 80% test coverage and no syntax errors before completion.

Traditional workflows implement code first, then add tests. Test-driven development inverts this: write failing tests first, implement code to pass them, then refactor. This Skill enforces this cycle with automated acceptance verification, deterministic file operations, and coverage thresholds to catch issues early and ensure production-ready code.