definition-of-done

To standardize Definition of Done checklists, this skill reads project-specific configurations from a centralized contract and applies them consistently across ticket refinement, QA planning, and issue closure workflows to prevent quality standard drift.

A centralized contract for Definition of Done management is a single canonical source file that stores project-specific checklists, ensuring all team members use identical quality criteria and preventing inconsistent standards across different artifacts.

Yes, you can generate ticket-specific quality assurance checklists. The skill automatically filters and formats checklist output based on the specific ticket type, such as frontend, backend, or DevOps, and applies the correct tracker markup.

Yes, you need a project contract file. The skill requires access to this centralized configuration file to determine the correct ticket types and checkbox formatting required for generating the appropriate Definition of Done checklists.

You should use an automated Definition of Done checklist during ticket refinement to automatically append the correct regression testing and QA requirements to the ticket body, ensuring consistent quality standards before development begins.