sprint-planning-helper
Sprint Planning Helper - Auto-activating skill for Enterprise Workflows. Triggers on: sprint planning helper, sprint planning helper Part of the Enterprise Workflows skill category.
36
Quality
3%
Does it follow best practices?
Impact
97%
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/sprint-planning-helper/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 lacking in substance. It provides only a skill name and category metadata without explaining any actual capabilities, use cases, or meaningful trigger terms. The description would fail to help Claude distinguish when to use this skill versus others.
Suggestions
Add specific capabilities the skill provides, e.g., 'Estimates story points, calculates team velocity, distributes work across sprints, identifies capacity constraints'
Include a 'Use when...' clause with natural trigger terms like 'sprint planning', 'backlog grooming', 'story points', 'velocity', 'sprint capacity', 'iteration planning'
Remove the redundant trigger term ('sprint planning helper' listed twice) and replace with varied natural language users would actually use
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Sprint Planning Helper' is just a name, and 'Auto-activating skill for Enterprise Workflows' is vague meta-description that doesn't explain 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 explicit use cases or triggers beyond the skill name). Both components are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sprint planning helper' repeated twice, which is the skill name itself rather than natural user language. Missing terms like 'sprint', 'backlog', 'story points', 'velocity', 'capacity planning' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'sprint planning' does provide some domain specificity to agile/scrum contexts, which reduces conflict with unrelated skills. However, without concrete actions, it could still overlap with other agile-related 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 an empty template with no actual content. It describes what a sprint planning helper should do but provides zero actionable guidance, no examples, no workflows, and no concrete instructions. The entire content could be replaced with actual sprint planning methodology, story point estimation techniques, capacity planning formulas, or meeting facilitation scripts.
Suggestions
Add concrete sprint planning workflows: backlog grooming steps, capacity calculation formulas, velocity tracking methods with specific examples
Include executable templates or checklists for sprint planning meetings (e.g., agenda template, definition of ready checklist, commitment criteria)
Provide specific examples of story point estimation, sprint goal formulation, and task breakdown with before/after comparisons
Replace generic capability claims with actual instructions Claude can follow, such as 'To calculate team capacity: available_days × focus_factor × hours_per_day'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | The skill contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for sprint planning. It only describes what it claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | There is no workflow defined whatsoever. The skill mentions 'step-by-step guidance' but provides none. No sequence, no validation steps, no actual process for sprint planning. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, templates, or related documentation that would provide actual sprint planning guidance. | 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.