roadmap-planning

Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is a well-sequenced, actionable roadmap-planning workflow with concrete examples and clear validation/feedback steps, but it is verbose (a large conceptual Key Concepts section and a redundant end-to-end summary) and its progressive disclosure is weak: it references template.md and examples/sample.md that are not bundled, leaving a monolithic body. Tightening the conceptual sections and actually offloading the fill-in structure/examples into the referenced files would lift the lower dimensions.

Suggestions

Cut the 'Key Concepts' block (Types of Roadmaps, Why This Works, Anti-Patterns, When to/Not to Use) to a few lines or move it to a reference — Claude already knows this general PM material and it inflates the token budget.

Create the referenced template.md and examples/sample.md bundle files (or remove the dangling references) so progressive disclosure resolves one level deep instead of pointing at non-existent paths.

Drop the 'Complete Workflow: End-to-End Summary' section since it restates the five phases already detailed above, removing the main redundancy.

Dimension	Reasoning	Score
Conciseness	The body is efficient in the phases but spends a large "Key Concepts" block (What is Strategic Roadmap Planning, Types of Roadmaps, Why This Works, Anti-Patterns) explaining general PM knowledge Claude already has, and an end-to-end summary that repeats the phase list; not 1 because the phase sections are genuinely actionable rather than pure padding.	2 / 3
Actionability	Concrete copy-paste-ready guidance throughout: the epic-hypothesis format with three worked example epics, a populated RICE scoring table, ASCII roadmap layouts, and per-phase questions/outputs; for an instruction-only skill the guidance is specific and executable rather than abstract.	3 / 3
Workflow Clarity	Five phases are clearly sequenced with day/week timing, goals, activities, and outputs, plus explicit validation/feedback checkpoints (Phase 4 "Validate with Engineering," Phase 5 "Gather Feedback" and "Refine Roadmap") and a pitfalls section for error recovery; not 2 because the checkpoints are explicit, not implicit.	3 / 3
Progressive Disclosure	References to template.md, examples/sample.md, and several skills/*/SKILL.md are signaled but no bundle files exist, and the detailed phase/example content that should live in those separate files is inlined into a ~500-line SKILL.md; not 1 because sections are well-organized rather than a monolithic wall, but the content that should be split is inline and the referenced paths do not resolve.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description follows the strong-example template precisely: a third-person action statement listing concrete capabilities plus an explicit 'Use when' trigger with natural terms. It cleanly answers what the skill does and when to invoke it without verbosity or over-claiming.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "prioritization, epic definition, stakeholder alignment, and sequencing" — matching the score-3 anchor of multiple specific concrete actions rather than a single domain label.	3 / 3
Completeness	Explicitly states both what ("Plan a strategic roadmap across...") and when ("Use when turning strategy into a release plan that teams can execute"), satisfying the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural PM-facing terms a user would actually say ("strategic roadmap," "prioritization," "sequencing," "release plan," "strategy") give good coverage; not below 2 because the vocabulary is common user language, not internal jargon like "document object model manipulation."	3 / 3
Distinctiveness Conflict Risk	The trigger "turning strategy into a release plan that teams can execute" carves a clear niche distinct from pure prioritization or strategy skills; not 2 because the release-plan/sequencing framing is unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (518 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/roadmap-planning/SKILL.md
Commit: 9971018

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.