The scenario
The list uses the repository’s existing pagination mechanism. Item identity and deterministic ordering are available.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
Exact IDs catch errors that a test of page length alone would miss.
A concrete outcome
Fix duplicate or missing records when loading the next page of a stable result set.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Reproduce the boundary case and inspect cursor or offset handling. Preserve the public response shape and avoid unrelated sorting changes.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Verify first page, next page, final partial page and empty result. Assert exact item IDs across page boundaries, not only counts.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.