Write, review, or rewrite Acceptance Criteria for user stories. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, rewrite, or review acceptance criteria, turn a user story into AC, translate behavior specs into Given/When/Then, critique existing Gherkin scenarios, define the "definition of done" for a story, or expand on a story's expected behavior — ev
Receba novas skills de Desenvolvimento toda segunda
1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
Acceptance Criteria
AC are always in English, regardless of input language.
What Acceptance Criteria are (and aren't)
AC are conditions a user story must satisfy to be considered complete. Each criterion has a binary, unambiguous pass/fail outcome. They serve three purposes simultaneously:
Shared understanding — align Product, Dev, QA on what "done" means before code is written.
Scope boundary — define the story's edges; make out-of-scope explicit.
**Test contr
[Description truncada. Veja o README completo no GitHub.]
