definition-of-done

Name: definition-of-done
Availability: InStock
Author: CivicActions

Generate Definition of Done checklists from project contract configurations.

2|Updated May 24, 2026

Search Tags:#project management #quality assurance #checklist #standardization #definition of done #ticket refinement

Ready to run

npx skills add https://github.com/CivicActions/ai-runbook-jh --skill definition-of-done-civicactions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: definition-of-done
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/definition-of-done
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill definition-of-done-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents inconsistencies in project quality standards by providing a single, canonical source for Definition of Done (DoD) checklists, ensuring they do not drift across different tickets or artifacts.

Core Features & Use Cases

Centralized DoD Management: Pulls project-specific checklists directly from the project contract, ensuring all team members use the same criteria.
Context-Aware Output: Automatically filters and formats checklists based on ticket type (e.g., FE, BE, DevOps) and tracker-specific markup.
Use Case: When refining a frontend bug ticket, invoke this skill to automatically append the correct regression testing and QA requirements to the ticket body.

Quick Start

Use the definition-of-done skill to generate the appropriate checklist for this frontend bug ticket.

Frequently Asked Questions about definition-of-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize Definition of Done checklists across different project tickets?▼

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.

What is a centralized contract for Definition of Done management?▼

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.

Can I generate ticket-specific quality assurance checklists for different ticket types?▼

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.

Do I need a project contract file to generate Definition of Done checklists?▼

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.

When should I use an automated Definition of Done checklist during ticket refinement?▼

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.