Name the proof up front
A task’s validation section turns ‘make it work’ into a concrete executable check. The agent can then discover a broken command early instead of choosing a convenient substitute at the end.
Answer page
How to prevent coding agents from skipping validation
Put executable validation in the task contract, require the observed result in the implementation summary, and treat missing evidence as incomplete work.
Direct answer
Do not rely on an agent remembering to test. Declare the exact validation command before implementation, require its observed result in the implementation summary, and block acceptance when the evidence is missing, failed, or out of scope.
Practical guidance
Make the next review decision easier.
Record results, not intentions
The implementation summary should state the command run and the result observed. A claim that tests were run without the command or outcome is not sufficient review evidence.
Reconcile against acceptance
Use reconciliation to see whether validation evidence covers each milestone criterion. If an item has no adequate evidence, keep it open for human decision or a follow-up task.
Verified demo evidence
A public prompt and outcome, not a completion claim.
This prompt and outcome are from the website’s checked-in synthetic repository demo. Substitute your own repository paths and declared validation gates when you apply the workflow.
Repository-writing command
Prompt: "Run the declared test gate for this repository scope."
outcome: 1 test passed; 0 failedAuthorship and sources
Trace this guidance to maintained product evidence.
- Maintainer
- Tianna McCoy ↗Day Shift maintainer; responsible for the repository-native workflow and release evidence referenced here.
- Last updated
- Tested Day Shift
- v0.2.26
Keep exploring
Follow the next question, not a generic funnel.
How to Make AI Coding-Agent Work Reviewable
Make coding-agent work reviewable with bounded repository artifacts, named validation, and written implementation evidence.
Read nextA Practical Coding-Agent Handoff Checklist
A practical checklist for handing work to a coding agent and receiving reviewable implementation evidence back.
Read nextInteractive Demo
Replay a fresh Day Shift lifecycle, inspect generated artifacts, and play the implemented Tic-Tac-Toe result.
Read nextFind your answer
Have we answered your question?
Search practical answer pages and product context, then follow each result to the canonical workflow or reference owner.
Search by a problem, workflow step, or tool boundary, or choose a filter.