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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sprint-planning-helperActivation
7%This description is severely lacking in substance. It provides no information about what the skill actually does, relying entirely on the skill name to convey meaning. The trigger terms are redundant repetitions of the skill name rather than natural user language, and there's no guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates sprint backlogs, estimates story points, calculates team velocity, and generates capacity plans'
Include a 'Use when...' clause with natural trigger terms like 'sprint', 'backlog grooming', 'story points', 'velocity', 'sprint capacity', 'iteration planning'
Remove the redundant trigger term repetition and replace with varied natural language users would actually use when requesting sprint planning assistance
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's a 'helper' for sprint planning without describing what it actually does - no verbs like 'creates', 'analyzes', 'generates', etc. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no meaningful 'Use when...' guidance - just a circular reference to the skill name. | 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 users would actually say like 'sprint', 'backlog', 'story points', 'velocity', 'capacity planning'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'sprint planning' does provide some domain specificity that distinguishes it from generic document or code skills, but without concrete actions described, it could still conflict with other agile/project management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It describes capabilities without providing any concrete guidance, code, workflows, or actionable instructions for sprint planning. The entire content could be replaced with actual sprint planning techniques, estimation methods, or backlog grooming processes.
Suggestions
Add concrete sprint planning workflows: capacity calculation, story point estimation, velocity tracking, and sprint goal definition with specific examples
Include executable code or templates for sprint artifacts (e.g., sprint backlog format, burndown chart data structure, capacity spreadsheet formulas)
Provide specific validation checkpoints: Definition of Ready checklist, sprint commitment criteria, and sprint review/retrospective templates
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual sprint planning techniques and decision frameworks
| 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. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. 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, and no structured navigation to actual sprint planning resources. | 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.