definition-of-done-generator
Definition Of Done Generator - Auto-activating skill for Enterprise Workflows. Triggers on: definition of done generator, definition of done generator Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill definition-of-done-generatorActivation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or providing meaningful trigger guidance. The redundant trigger terms and lack of concrete actions make it nearly impossible for Claude to understand when to select this skill over others. The only slight positive is that 'Definition of Done' is a somewhat specific domain term.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates acceptance criteria checklists, creates testable completion requirements, and validates user story readiness for agile teams.'
Include a 'Use when...' clause with natural trigger terms like 'DoD', 'done criteria', 'acceptance criteria', 'story completion checklist', 'sprint deliverable requirements', or 'agile definition of done'.
Remove the duplicate trigger term and expand with variations users would naturally say when needing this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Definition Of Done Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates acceptance criteria', 'generates checklist items', or 'validates completeness'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful context for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant (lists 'definition of done generator' twice) and overly specific. Missing natural variations users would say like 'DoD', 'done criteria', 'acceptance criteria', 'user story completion', or 'sprint deliverables'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Definition of Done' is fairly specific to agile/scrum contexts, which provides some distinctiveness. However, the vague 'Enterprise Workflows' category and lack of specific triggers could cause overlap with other agile or documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It describes what a skill should do in generic terms but provides zero actionable guidance on generating definitions of done. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add concrete examples of definition of done criteria for different contexts (user stories, sprints, features) with actual templates Claude can use
Include a step-by-step workflow for generating a DoD: gather requirements → identify acceptance criteria → define quality gates → format output
Provide executable output formats (markdown checklist template, JSON schema for structured DoD) that Claude can populate
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of what a 'definition of done' looks like or how to generate one. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There's no process, no sequence, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no meaningful structure. There are no references to detailed materials, no examples to link to, and the sections present contain only generic placeholder text. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.