outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./pm-execution/skills/outcome-roadmap/SKILL.md

Quality

Content

67%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 body is a well-structured, actionable guide with a usable template and worked example, but it carries conceptual padding in the Context and Notes sections and lacks an explicit validation checkpoint for testing outcome statements. Tightening the prose and adding a measurable-outcome checkpoint would lift the weakest dimensions.

Suggestions

Trim the Context section and dedupe the Notes against the Instructions so the body adds only what Claude does not already know about output-vs-outcome roadmaps.

Add an explicit validation step to the workflow (e.g., 'Verify each outcome is measurable and names a metric; if not, ask "So what?" and rewrite') with a feedback loop rather than burying the testability check in Notes.

Cover an edge case in the Transformation Process, such as initiatives that do not map cleanly to a single outcome or lack an obvious business metric.

Dimension	Reasoning	Score
Conciseness	The Context section restates why output-focused roadmaps fail ('create false precision and misalign teams around features rather than results') and Notes overlap with the Instructions, adding explanation Claude does not need; this matches anchor 3 rather than 4 which allows only minor over-explanation.	3 / 5
Actionability	Provides a concrete fill-in template ('Enable [customer segment] to [desired customer outcome] so that [business impact]') and a worked example with specific metrics, giving mostly executable guidance with minor gaps around initiatives that do not map cleanly.	4 / 5
Workflow Clarity	A clear 7-step numbered sequence runs from gathering information to saving output, but the 'testable and measurable' check lives in Notes rather than as an explicit validation checkpoint, and the 'So what?' retry is soft, placing this at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist, so structure is scored on the body: well-organized sections (Purpose, Context, Instructions, Notes) with clearly signaled external 'Further Reading' links, but at ~64 lines it exceeds the simple-skill threshold and the external references are not one-level-deep local files, so anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

78%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 strong: it clearly states what the skill does and gives explicit, natural trigger phrases for when to use it. Its main weakness is specificity, listing only a couple of concrete actions rather than comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('Transform an output-focused roadmap into an outcome-focused one', 'Rewrites initiatives as outcome statements'), matching anchor 3 rather than 4 since it does not list several specific actions.	3 / 5
Completeness	Explicitly answers both what ('Transform... Rewrites initiatives as outcome statements') and when ('Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural PM phrases appear ('outcome roadmaps', 'roadmap more strategic', 'feature lists as outcomes', 'shifting to outcome roadmaps') with good synonym coverage, falling just short of anchor 5 which expects exhaustive term coverage.	4 / 5
Distinctiveness Conflict Risk	The outcome-roadmap transformation is a clear niche, but the broad terms 'roadmap' and 'strategic' carry minor overlap risk with generic planning or strategy skills, so it sits at anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-execution/skills/outcome-roadmap/SKILL.md
Commit: 18468a9

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.