CtrlK
BlogDocsLog inGet started
Tessl Logo

roadmap-planning

Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, highly actionable planning skill with a clear sequenced workflow, validation checkpoints, and proper progressive disclosure via a single one-level-deep reference. Its only weakness is length — the body could be tightened without losing substance.

Suggestions

Trim stylistic flourishes (e.g., "A roadmap without strategy is just a queue") and condense the capacity-defaults list to reduce body length toward the lean conciseness anchor.

Move the inline framework one-liners (RICE/MoSCoW/Kano formulas) fully into the reference file since the reference already covers them in depth, keeping the body to the choice guidance.

Consider splitting the detailed capacity-model and output-format specs into a second reference file so the SKILL.md body reads as a tighter overview.

DimensionReasoningScore

Conciseness

Largely dense and signal-bearing with little padding of Claude-known basics, but at ~220 lines with some stylistic prose ("A roadmap without strategy is just a queue") it is mostly efficient yet could be tightened — matching the level-2 rather than the lean level-3 anchor.

2 / 3

Actionability

Concrete, executable guidance throughout: capacity defaults (engineers 60-70%, designers 50-60%), the S/M/L/XL size scale, 3-5 theme limit, default cadence, per-step required outputs, and audience-specific communication views.

3 / 3

Workflow Clarity

A clearly sequenced 8-step workflow with explicit validation checkpoints and feedback loops — "If the strategy is missing or vague, stop," Step 6 "Validate with the team," and "If the team says the plan is impossible... Adjust" — plus a failure-patterns section for error recovery.

3 / 3

Progressive Disclosure

Well-organized body split into focused sections with one well-signaled, one-level-deep reference (references/prioritization-frameworks.md, linked in Step 3 and the Reference files section); verified the reference contains no nested links, so navigation stays shallow.

3 / 3

Total

11

/

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.

A strong description: third-person voice, concrete actions, explicit "Use when"/"Triggers on" guidance, and rich natural trigger terms covering both keyword and conversational phrasings. It cleanly distinguishes itself from neighboring PM skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Build a multi-quarter roadmap," "sequencing dependent work," "balancing build vs improve vs maintain," "making the case for what NOT to do" — matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what ("Build a multi-quarter roadmap from a backlog...") and when ("Use this skill when planning the next quarter..." plus "Triggers on..." and "Also triggers when...").

3 / 3

Trigger Term Quality

Broad coverage of natural terms users would say — "roadmap," "quarterly planning," "what should we build next," "sequencing," "prioritization," "OKR planning," "capacity planning," "what's on the roadmap," "plan the year," "what to ship next quarter," plus a stakeholder-conflict phrase.

3 / 3

Distinctiveness Conflict Risk

Clear roadmap-planning niche with specific triggers; the body's "When NOT to use" section names sibling skills (pm-spec-writing, ux-research, design-standards, launch-runbook, after-action-report), reinforcing low conflict risk.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.