atdd-assistant

To write acceptance criteria in Given-When-Then format for user stories, you define the initial context, the action taken, and the expected outcome. This Skill facilitates specification workshops to convert these criteria into executable tests, ensuring unambiguous requirements.

The best way to run a specification workshop for ATDD is to collaboratively define user stories and validate them against INVEST criteria. This Skill guides teams through the entire workflow, ensuring stakeholders agree on what 'done' means before coding begins.

ATDD workflow integrates with BDD and TDD practices by bridging collaborative requirement definitions with executable testing. This Skill guides the transition from specification workshops through test distillation and development, validating acceptance criteria throughout the agile cycle.

Yes, you can validate user stories against INVEST criteria before development. This Skill provides dedicated templates for user stories and acceptance criteria, supporting the evaluation of stories to ensure they are actionable and verifiable.

The main stages of the Acceptance Test-Driven Development cycle are Workshop, Distillation, Development, Demo, and Done. This Skill guides teams sequentially through these stages to ensure collaborative development and verifiable software.