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.
36
3%
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
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 extremely weak across all dimensions. It reads as an auto-generated stub with no substantive content—no concrete actions, no natural trigger terms beyond the skill's own name repeated, and no guidance on when Claude should select it. It would be nearly impossible for Claude to make an informed decision about when to use this skill over alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Prioritizes backlog items, writes user stories and acceptance criteria, estimates story points, and identifies dependencies between tickets.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about backlog grooming, sprint planning, story refinement, ticket prioritization, writing user stories, or estimating effort for agile teams.'
Remove the redundant duplicate trigger term and replace the auto-generated boilerplate with a substantive description that distinguishes this skill from other agile/project management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Backlog Grooming Assistant') and mentions a category ('Enterprise Workflows') without describing what it actually does—no verbs, no capabilities, no outputs. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no meaningful 'Use when...' clause—only a redundant trigger phrase and a category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'backlog grooming assistant' repeated twice. These are not natural keywords a user would say; users are more likely to say things like 'groom the backlog', 'prioritize stories', 'refine tickets', 'sprint planning', or 'user stories'. The terms are overly specific to the skill name itself rather than user language. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'backlog grooming' is somewhat niche and unlikely to conflict with many other skills, but the lack of specificity about what it actually does (e.g., does it prioritize, estimate, write acceptance criteria?) means it could overlap with other agile/project management skills without clear differentiation. | 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 entirely a placeholder/template with no substantive content. It repeatedly references 'backlog grooming assistant' without ever defining what that means or providing any actionable guidance. There are no concrete steps, code examples, commands, or references to external resources—it is functionally empty.
Suggestions
Define what 'backlog grooming' actually entails in this context and provide concrete steps (e.g., how to prioritize items, estimate effort, identify dependencies, split stories).
Add actionable examples such as a sample backlog item before/after grooming, a template for story refinement, or specific commands/tools to use.
Include a clear multi-step workflow with validation checkpoints (e.g., 1. Review items → 2. Estimate → 3. Prioritize → 4. Validate acceptance criteria are complete).
Either keep the skill concise and focused on a single task with executable guidance, or provide an overview with links to detailed sub-documents for different grooming activities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. The phrase 'backlog grooming assistant' is repeated excessively without ever defining what it actually does. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no specific steps, no examples of actual backlog grooming workflows. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' no steps are actually listed. There are no sequences, validation checkpoints, or processes of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings. | 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
4dee593
- 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.