The scenario
The list already works and has a search input or an established input component 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
Examples and non-goals make a small feature implementable without inviting a search-framework redesign.
A concrete outcome
Add case-insensitive title filtering to the existing list. An empty query must preserve every item in its current order.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Inspect the existing list and tests. Reuse current UI conventions; add no fuzzy search, new dependency or persistence behavior.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Check mixed-case matches, no match, empty input and stable order. Inspect the diff for unrelated changes.
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.