The vague version hides important decisions
This does not say whether to follow the operating system, provide a switch, persist the preference, change every page, or test mobile and keyboard use. The agent would have to choose for you.
Weak request
Add dark mode to the site and make it look good.Ask only the questions that change the outcome
- What should the user see and do?
- Which pages and components are in scope?
- What happens on the first visit?
- Should the choice survive a reload?
- What must remain unchanged?
- How will keyboard access, contrast, and mobile layout be checked?
Write an executable task
Task brief
Goal: Add a light/dark theme switch to the existing site.
User flow: Open the main menu, choose a theme, see the change immediately, and keep the choice on later visits.
Scope: Header, global styles, and current menu pages. Store the choice in localStorage.
Constraints: On a first visit use the system preference. Add no library. Keep readable contrast and visible keyboard focus. Do not change copy, routing, or page structure.
Acceptance criteria: The switch works with mouse and keyboard; choice survives reload; text remains readable in both themes; no horizontal overflow at 390px; production build passes.
Verification: Try first visit, switch, and reload. Inspect home and one internal page on desktop and mobile. Report anything unverified.Turn wishes into observable criteria
“Modern” or “easy to use” does not tell a reviewer when the task is done. “At 390px there is no horizontal scrolling, and the main button remains visible” can be checked. Describe success, the important error state, and the main edge case without prescribing an unnecessary implementation.
Form example
Vague: The form should work and handle errors.
Checkable: Submit stays disabled until required fields are filled. An invalid email shows a message by its field. A successful submission shows confirmation and clears the form. A failed submission preserves entered data. Every field is reachable by keyboard.Check the task before handing it over
Every criterion should describe something you can observe and answer yes or no. For multi-state flows, Given / When / Then can make the context and expected result explicit.
Given / When / Then
Given the cart contains one product
When the user removes it
Then the cart shows its empty state
And the total is no longer displayed