backlog-grooming-assistant
Backlog Grooming Assistant - Auto-activating skill for Enterprise Workflows. Triggers on: backlog grooming assistant, backlog grooming assistant Part of the Enterprise Workflows skill category.
34
Quality
0%
Does it follow best practices?
Impact
98%
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/backlog-grooming-assistant/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It only provides the skill name, a redundant trigger, and a vague category label. It completely fails to describe what the skill does, what actions it performs, or when it should be selected over other skills.
Suggestions
Add specific capabilities using action verbs (e.g., 'Prioritizes backlog items, writes user stories, defines acceptance criteria, estimates story points, identifies dependencies between tickets')
Add a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions sprint planning, story refinement, backlog prioritization, ticket grooming, or needs help writing user stories')
Remove the redundant trigger term and replace with varied natural language users would actually say when needing backlog grooming help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Backlog Grooming Assistant' is just a name, not a description of capabilities. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no use cases or explicit triggers beyond the skill name). Both components are missing entirely. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'backlog grooming assistant' repeated twice, which is the skill name itself rather than natural user language. Missing terms like 'prioritize tickets', 'refine stories', 'sprint planning', 'user stories', 'acceptance criteria'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no clear niche. 'Enterprise Workflows' is extremely broad and could conflict with any business-related skill. No specific domain boundaries are established. | 1 / 3 |
Total | 4 / 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 template with no actual content. It repeatedly references 'backlog grooming assistant' without ever defining what that means or providing any actionable guidance. The skill fails on all dimensions because it contains only meta-descriptions of what a skill should do rather than actual instructions.
Suggestions
Define what 'backlog grooming' actually involves - add concrete steps like prioritization criteria, story point estimation methods, or acceptance criteria templates
Add executable examples such as sample user story formats, grooming session agendas, or scripts for extracting/organizing backlog items from project management tools
Include a clear workflow with validation checkpoints, e.g., '1. Review stories without estimates 2. Check for missing acceptance criteria 3. Validate dependencies are documented'
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 actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual backlog grooming tasks. The skill describes what it claims to do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. Despite claiming to provide 'step-by-step guidance,' the skill contains no actual steps, sequences, or processes for backlog grooming. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful content. | 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.