Enforce RED/GREEN/REFACTOR phases with Given/When/Then acceptance tests.
npx skills add https://github.com/jikig-ai/soleur --skill atdd-developer
Please help me install this Agent Skill. Skill: atdd-developer Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/atdd-developer Command: npx skills add https://github.com/jikig-ai/soleur --skill atdd-developer
Guides developers to implement features reliably by enforcing an Acceptance Test Driven Development cycle that ensures tests define behavior before implementation and prevents skipping critical phases.
Write Given/When/Then acceptance tests for the feature, run them to confirm they fail, and ask to proceed to the next phase.
High-intent search queries and answers about installing and using this skill.
Acceptance test driven development (ATDD) implements user stories by writing Given/When/Then acceptance tests, confirming they fail, writing minimal code to pass them, and then refactoring while keeping tests green. This enforces a structured RED/GREEN/REFACTOR cycle.
The RED/GREEN/REFACTOR cycle in test driven development enforces writing failing acceptance tests first, implementing the smallest code change to make them pass, and then safely refactoring while running the full test suite to prevent regressions.
Writing acceptance tests in Given/When/Then format for new features requires defining the initial context, the triggering action, and the expected outcome before any implementation begins. These tests must fail initially to validate the RED phase.
Preventing phase skipping during test driven development requires explicit user confirmation gates before moving between RED, GREEN, and REFACTOR phases. This ensures failing tests are written first and the full suite runs after each change.
ATDD works with conventional commits by producing structured commit messages after each completed RED/GREEN/REFACTOR cycle. This ensures feature implementation history aligns with the acceptance tests and iterative refactors.
You should not use acceptance test driven development when implementing exploratory spikes or throwaway prototypes where writing formal Given/When/Then acceptance tests and maintaining a full test suite creates unnecessary overhead.
nholder88Convert vague requirements into Given/When/Then acceptance criteria and specifications.
vm0-aiAutomate GitHub issue continuation with feature branches, conventional commits, and tests.
kaptinlinEnforce red-green-refactor TDD cycles for feature implementation.
gztcodeEnforce a RED-GREEN-REFACTOR cycle by writing tests before implementation in Python.
