roadmap-generator
Roadmap Generator - Auto-activating skill for Enterprise Workflows. Triggers on: roadmap generator, roadmap generator 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 roadmap-generatorActivation
7%This description is severely underdeveloped, essentially providing only the skill name without any meaningful detail about capabilities or usage triggers. It fails to help Claude distinguish when to select this skill, as it lacks concrete actions, natural trigger terms, and explicit guidance on when to use it. The redundant trigger terms and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates visual product roadmaps, generates timeline charts, organizes features by priority and release phase, exports roadmap documents'
Include a proper 'Use when...' clause with natural trigger terms: 'Use when the user asks about product roadmaps, release planning, feature timelines, milestone tracking, or quarterly planning'
Add varied trigger terms users would naturally say: 'product roadmap', 'release plan', 'feature timeline', 'quarterly goals', 'milestone chart', 'strategic planning'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Roadmap Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates timeline visualizations', 'prioritizes features', or 'generates milestone charts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' line is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('roadmap generator, roadmap generator') and extremely limited. Missing natural variations users would say like 'product roadmap', 'project timeline', 'release plan', 'feature planning', or 'milestone planning'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'roadmap' is somewhat specific to planning/product management, the lack of detail about what kind of roadmaps or for what purpose could cause overlap with project management, planning, or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially an empty placeholder that describes what a roadmap generator skill might do without providing any actual content. It contains no executable guidance, no examples of roadmap formats, no templates, and no concrete steps for generating roadmaps. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add concrete examples of roadmap formats (e.g., Gantt chart structure, milestone templates, or Mermaid/PlantUML syntax for visual roadmaps)
Provide executable code or templates for generating roadmaps in common formats (Markdown tables, JSON schema, or project management tool exports)
Define a clear workflow: gather requirements → identify milestones → estimate timelines → generate output format → validate completeness
Include at least one complete input/output example showing what information is needed and what a generated roadmap looks like
| 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 generating roadmaps. 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 roadmap generation. | 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 supporting documentation that would actually help with roadmap generation. | 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.