finish

To verify changes meet a definition of done, execute a final end-of-work check that runs verification steps, tightens contracts and docs, and confirms boundary discipline for release readiness.

Generate a change summary by finalizing verification, tightening documentation to reflect the change, and packaging a concise executive and engineer packet communicating what changed and why.

Finalize documentation and contract tightening by executing verification steps that ensure contracts, docs, and release notes accurately reflect the change and maintain traceability across code and docs.

Definition of done checks can be used for both code and documentation updates, covering non-trivial changes across both domains to ensure complete release readiness and traceability before merge.

An executive and engineer packet includes a concise change summary generated from final verification steps, tightened contracts, and updated documentation communicating what changed and why for merge readiness.

Run a final definition of done check when you need to turn half-done changes into shipping-ready readiness by executing verification, tightening contracts, and producing a formal traceability summary beyond standard review.