Owner role · Engineer
Evidence: An invented valid account receives a reset link and can set a new password in the test environment.
Task planning / Task reviewers
Readiness checklistWrite acceptance criteria that settle a task
Define observable acceptance evidence so a reviewer can decide whether a task is complete without guessing.
Use a concrete behavior, a boundary case and a reviewer decision instead of a generic done checkbox.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Check the evidence before proceeding
Local readiness checklistIllustrative case: a password-reset task says “improve the reset experience.” The team needs to agree what the reviewer should actually inspect.
Owner role · QA reviewer
Evidence: An expired link receives the agreed safe error state without exposing account information.
Owner role · Task owner
Evidence: The reviewer links the test evidence and records accepted or changes requested.
0 of 3 checks marked locally.
Checking boxes records your review here; it does not verify product data or save anything.
Decision to make: Accept the task only after the agreed behaviors pass; record unresolved behavior as new scope.
Filled illustrative decision
Invented planning text. Adapt it to your evidence and confirmed owners.
In the invented review, a valid reset link changes the password, while an expired link shows the agreed error without revealing account details. The reviewer accepts those bounded behaviors. A proposed redesign of the email is recorded separately, because it was not part of the original acceptance criteria.
Put the outline to work
- Replace “works well” with the user behavior that must be observed.
- Choose a realistic failure case and agree the expected response before implementation.
- Have the reviewer compare the evidence against the original criteria, not a moving target.
Questions about this workflow
Should every task have many criteria?
No. Add the smallest set that distinguishes success from failure. A small copy edit may need only the final wording and approval.
Can criteria change during work?
Yes, but document the change and reassess scope with the owner. Do not silently add acceptance conditions at review.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
From a useful outline to team work
Explore TeamBoostAI for your team
Use these behavior and boundary checks when reviewing a TeamBoostAI task description; a status change alone does not prove acceptance. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.