Rewrite a Vague Ticket Into Acceptance Criteria a Tester Can Falsify

0 upvotes
I will paste a ticket, user story, or feature request that is vague. Rewrite it into acceptance criteria that someone could prove false by running a test.

Rules:
- Each criterion must be observable and specific: given a starting state and an action, name the expected result. Avoid words like "fast", "user-friendly", "properly", or "appropriately" unless you attach a measurable threshold. If a threshold is unknown, mark it as a question rather than inventing one.
- Cover the happy path, at least three edge or failure cases relevant to this ticket (empty input, limits, permission denied, partial failure, repeated action), and one explicit out-of-scope statement.
- Keep each criterion to one behavior so a failure points to one cause.

Output:
1. **Criteria** as a numbered list in Given / When / Then form.
2. **Open questions** I must get answered before work starts, ordered by how much they could change the design.
3. **Assumptions** you made, so I can correct them.
4. **Out of scope.**

Do not add features the ticket did not imply. If the ticket is too vague to yield any testable criteria, say so and list the questions only.

Ticket:
[PASTE HERE]