definition-of-done-generator

Quick Review

The skill has clear structure and proper formatting, but suffers from extremely vague and circular descriptions that provide no concrete information about what a 'definition of done' actually is or how to generate one. The description merely repeats the skill name without explaining the task (e.g., creating completion criteria for agile stories/sprints). No actual methodology, templates, or implementation steps are provided. A CLI agent would not understand what to do beyond recognizing trigger phrases. The novelty is low-moderate since generating DoD checklists is straightforward for modern LLMs. To improve: add concrete explanation of DoD concept, provide templates/frameworks (INVEST criteria, acceptance criteria patterns), include examples for different contexts (user stories, sprints, releases), and add validation logic for completeness.