backlog-grooming-assistant
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill backlog-grooming-assistantBacklog Grooming Assistant - Auto-activating skill for Enterprise Workflows. Triggers on: backlog grooming assistant, backlog grooming assistant Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It provides only a title and category without explaining what the skill does, what actions it performs, or when it should be selected. The duplicate trigger term suggests this may be auto-generated boilerplate that was never properly filled in.
Suggestions
Add specific actions the skill performs, such as 'Prioritizes user stories, estimates story points, identifies dependencies, and prepares tickets for sprint planning'
Include a 'Use when...' clause with natural trigger terms like 'backlog refinement', 'sprint planning', 'story points', 'prioritize tickets', 'groom stories', or 'prepare for sprint'
Remove the duplicate trigger term and expand with variations users would naturally say when needing backlog grooming assistance
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Backlog Grooming Assistant' is a title, 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' beyond the title, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name without meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are duplicates of the skill name itself ('backlog grooming assistant' repeated twice). No natural variations like 'sprint planning', 'ticket refinement', 'story points', 'prioritize backlog', or 'groom stories' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'backlog grooming' is somewhat specific to agile/scrum contexts, which provides some distinctiveness. However, without describing actual capabilities, it could conflict with other agile-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It repeatedly references 'backlog grooming assistant' without ever defining what backlog grooming entails or providing any actionable guidance. The entire content could be replaced with actual instructions for prioritizing stories, estimating effort, splitting epics, or other concrete backlog grooming activities.
Suggestions
Add concrete examples of backlog grooming tasks: story prioritization criteria, estimation techniques (story points, t-shirt sizing), acceptance criteria templates
Include executable workflows such as: 1) Review story -> 2) Check acceptance criteria -> 3) Estimate complexity -> 4) Identify dependencies -> 5) Prioritize in backlog
Provide specific output formats or templates, e.g., a user story template, a prioritization matrix, or a sprint planning checklist
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual domain-specific 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 conveying 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 content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes documented for backlog grooming activities. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or templates, and no organization that would help Claude navigate to useful information. | 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.