Guide implementation from acceptance tests inward using Given/When/Then scenarios.
npx skills add https://github.com/scute-sh/scute --skill atdd-scute-sh
Please help me install this Agent Skill. Skill: atdd Source: https://github.com/scute-sh/scute/tree/main/.claude/skills/atdd Command: npx skills add https://github.com/scute-sh/scute --skill atdd-scute-sh
This Skill helps ensure that software is built to meet user needs by starting with acceptance tests and working inwards, preventing the development of features that don't align with desired behavior.
Describe the scenario in plain language first, then turn it into an acceptance test, and make the test pass by working outside-in.
High-intent search queries and answers about installing and using this skill.
Acceptance test-driven development (ATDD) drives software implementation from user-visible behavior inwards. You define expected outcomes as Given/When/Then scenarios, convert them into failing acceptance tests, and implement code layer by layer to make them pass.
To start outside-in development, describe the desired user-facing scenario in plain language, translate it into a failing acceptance test, and implement the necessary code while stubbing dependencies as you progress through each layer.
Use behavior-driven development when building behavior-heavy features, algorithm-heavy logic, or integration tests. It enforces a disciplined approach by prioritizing acceptance criteria and iterative refinement to ensure software meets user needs.
Acceptance test-driven development starts from user-visible behavior and works inwards using scenarios, while traditional test-driven development typically focuses on lower-level unit tests. ATDD prevents building features that do not align with desired behavior.
Yes, acceptance testing supports scenarios involving algorithm-heavy logic and integration testing through a structured outside-in build loop, ensuring implementation iteratively refines to meet the defined acceptance criteria.
Stubbing dependencies is required in outside-in development to isolate and progress layer by layer from user-visible behavior. It allows you to build and verify the outer acceptance criteria before implementing the inner logic.
TheBushidoCollectiveGenerate Gherkin Given-When-Then BDD scenarios with acceptance criteria and edge cases.
ourchitectureCompare Gherkin features, contract tests, and stack implementations to report coverage gaps.
randalmurphalGuide developers through red-green-refactor cycles for test-first implementation.
iCesofTApply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.
