A release marker can be accurate and still leave the real work unfinished. People need to know what happens after the code is labeled ready.
The practical check
Define the post-release checks before declaring success: what must be visible, who is affected, and what result proves the change reached the intended place.
Where AI fits
AI can organize release notes, expected outcomes, and follow-up checks into a review list.
The human decision
People authorize release completion and verify the outcome in the real environment.
The lesson
A release is complete only when the owner has checked the intended outcome, the follow-through work is clear, and the real result meets the completion criteria.
Post-release checks around the tagged code and its intended destination appear in the Build Log companion.
AI Skills
Use this lesson with the AI assistant you already use
Create a release, expected outcome, verification evidence, and owner table.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI agent
LESSON: Turn Release Into a Verified Outcome
WHAT TO SHARE:
A de-identified description of the work, current evidence, and the decision you are considering.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Create a release, expected outcome, verification evidence, and owner table.
3. Identify the narrowest useful next review step.
RETURN:
A short table with the evidence, uncertainty, human-owned decision, and next action.
BOUNDARY: Do not change records, contact anyone, route work, publish content, or act in an external system. A person must review the evidence and approve every consequential step.
