Run work verification and request fixes
Check finished work against its written requirements, then request focused fixes for clear misses.
Last updated 17 September 2026
Check finished work against its written requirements, then request focused fixes for clear misses.
Before you begin
Work verification is available for eligible agent work linked to a task, doc, or implemented plan with changed files. It is separate from Code Review and from the manual What to check checklist.
The demo’s completed verification reports all six requirements met. The manual What to check checklist remains a separate review step.
Steps
Open Settings → AI generation and choose the Work verification preference: Ask every time, Automatic, or Off.
Complete the implementation from the linked task, doc, or approved plan. Read the agent result and inspect its changed files before treating any summary as proof that the requirements are met.
When Verify this work? appears, choose Verify now for this result. Not now skips the current offer. Always verify also changes the future preference; Never verify turns the preference off.
Let the verification pass finish and read the requirement-level outcomes. Met means the verifier found supporting evidence; Missed identifies an unmet requirement; Unclear needs clarification or additional evidence.
If Ask to fix is available, review the clear misses and use it to request the focused corrections. Do not assume an unclear requirement has automatically become an implementation task.
After the fix pass, use Re-verify when prompted, or let Automatic mode run it. Inspect the latest result and any remaining uncertainty.
Perform the relevant manual checks and delivery review before shipping. Verification is another agent pass, not a guarantee that every runtime or product behavior was exercised.
What to expect
You have a visible record of how the implementation compares with its written requirements and can follow a fix-and-recheck cycle.
Troubleshooting
If no offer appears, check the setting, whether the conversation actually changed files, and whether it has a linked task/doc or implemented plan. An ordinary unlinked question, delegated specialist conversation, or design handoff may not meet the same eligibility rules. Verification takes additional time and provider usage. Clarify vague requirements before asking the agent to guess the intended behavior.