definition-of-done

To validate acceptance criteria coverage after a PR merge, run a post-merge check that compares the merged PR against the story's AC, test plan, and DoR artefacts, producing a DoD artefact that records coverage and deviations.

A definition of done artefact is a formal post-merge record that summarizes acceptance criteria coverage, test plan results, DoR artefact presence, and any deviations found during the validation process.

You generate a DoD artefact by invoking a post-merge validation flow that checks the merged PR against the test plan and DoR artefacts, automatically recording coverage status, test results, and any deviations.

Yes, post-merge validation requires DoR artefacts to confirm the full pipeline, checking that the PR is merged, artefacts exist, and the DoR confirms all required stages were satisfied before generating the DoD artefact.

The best way to handle deviations found during definition of done checks is to follow the guided next steps provided by the validation process, which help record decisions and manage any deviations from the acceptance criteria or test plan.

You need to run a definition of done validation flow when someone invokes a mark as done process after a PR merge, ensuring that all acceptance criteria, test plans, and DoR artefacts are formally validated and recorded.