Azure DevOps Definition of Done and Branch Policy Summary
Document done criteria and how policies enforce them.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a definition of done for [TEAM] and map it to Azure DevOps features. Our practices: [PRACTICES]. Branch policy settings in use: [BRANCH_POLICIES]. Automated checks: [CHECKS]. Give the criteria as a checklist in a table with Criterion, Where it is checked (pull request policy, pipeline, work item field or manual review), Responsible and Automatic or not. Note gaps where a criterion exists only in people's heads, and which criteria depend on judgement and cannot be automated. Explain each policy in a sentence a non-engineer can follow, for example 'a pull request needs one approving review before merge'. Note that the definition applies to every item, while acceptance criteria are specific to each. Mark settings you cannot confirm [VERIFY]. Propose a plan to close the biggest gap in one sprint, how new team members will learn the definition in their first week, and a review date. Keep the checklist to no more than ten criteria. If a criterion cannot be checked by anyone but its author, rewrite it so another person can verify it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.