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

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/roadmap-planning/SKILL.md

Quality

Content

56%Weight 40%Scale 1-5

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

The content is a well-sequenced, actionable workflow with strong concrete examples, but it is padded with conceptual explanation and duplication that hurts token efficiency, and its file references point to bundle files that are not present.

Suggestions

Trim the Key Concepts section (roadmap types, 'Why This Works', anti-patterns) and remove the verbatim duplication of the frontmatter intent in the Purpose section to improve conciseness.

Move the per-phase activity detail and large example blocks into referenced files (e.g., template.md, examples/sample.md) and ensure those files actually exist in the bundle.

Add an explicit validate-and-recover loop (e.g., re-score after stakeholder feedback invalidates priorities) to push workflow clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the Key Concepts section explains roadmap types and anti-patterns a competent PM/Claude likely knows, the Purpose section duplicates the frontmatter intent verbatim, and the End-to-End Summary repeats the phase details already listed above.	2 / 5
Actionability	Provides concrete, executable guidance — specific questions to ask, defined outputs per phase, example epic hypotheses with metrics, a worked RICE scoring table, and example roadmap trees — with only minor gaps where steps remain high-level.	4 / 5
Workflow Clarity	The five phases are clearly sequenced with day-level timing and per-phase outputs, and validation appears via 'Validate with Engineering' (Phase 4) and feedback-then-refine (Phase 5), though explicit error-recovery feedback loops are not fully spelled out.	4 / 5
Progressive Disclosure	Section headers and references to template.md and examples/sample.md provide some structure, but the bulk of the content (Key Concepts and all five detailed phases) is inlined rather than split out, and the referenced bundle files do not exist in the skill directory.	3 / 5
	Total	13 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 is concise, third-person, and clearly answers both what the skill does and when to use it with a concrete trigger. It is slightly limited by phase-level rather than action-level specificity and minor overlap with adjacent strategy skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete action areas — 'prioritization, epic definition, stakeholder alignment, and sequencing' — but these read as phases rather than fully concrete actions, leaving minor coverage gaps relative to the comprehensive anchor.	4 / 5
Completeness	Explicitly states both what ('Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing') and when ('Use when turning strategy into a release plan that teams can execute') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural PM terms like 'strategic roadmap', 'prioritization', 'release plan', and 'sequencing' that users would plausibly say, though common variations such as 'quarterly plan' or 'OKRs' are absent.	4 / 5
Distinctiveness Conflict Risk	The roadmap-planning niche is clearly staked out, but there is minor overlap risk with closely related strategy skills such as product-strategy-session and prioritization-advisor.	4 / 5
	Total	17 / 20 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: a03af68

Reviewed: 11 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.