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.
36
Quality
3%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/definition-of-done-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks concrete actions, natural trigger terms, and explicit usage guidance. 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 comprehensive Definition of Done criteria for user stories, features, and sprints based on team context and project requirements.'
Include a 'Use when...' clause with natural trigger terms like 'DoD', 'acceptance criteria', 'done criteria', 'story completion requirements', 'sprint deliverables', or 'agile definition of done'.
Remove the duplicate trigger term and expand to include 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 verbs explaining what the skill actually does - no mention of creating, generating, formatting, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'definition of done generator' repeated twice, which is redundant and overly specific. Missing natural variations users might say like 'DoD', 'acceptance criteria', 'done criteria', 'user story completion', or 'sprint requirements'. | 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%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no substantive content. It describes what a skill should do without providing any actual guidance, code, examples, or workflows for 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 templates for different contexts (user stories, sprints, features) with specific acceptance criteria formats
Provide a step-by-step workflow for generating a DoD: gather requirements → identify acceptance criteria → define verification methods → format output
Include executable code or structured templates that Claude can use to generate DoD documents, such as markdown templates or JSON schemas
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| 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. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no validation checkpoints or any process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples, and no structured navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.