The scenario
The app has a notification toggle, an API layer and persistent storage; documentation may be stale.
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
It asks for a concrete execution path and evidence instead of a generic architecture summary.
A concrete outcome
Explain how the notification preference travels from the settings UI to durable storage.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Stay read-only. Trace the actual field through callers, validation, authorization and persistence. Cite paths and symbols; separate observed behavior from assumptions.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Cross-check the trace against implementation and relevant tests. Identify any path that could overwrite or ignore the preference.
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.