CtrlK
BlogDocsLog inGet started
Tessl Logo

roadmap

Build evidence-backed software/product roadmaps from repo state, tickets, ideas, audit findings, or user goals — prioritize and sequence work across Now/Next/Later, milestones, dependencies, risks, and handoffs. Use when asked for a roadmap, feature roadmap, technical roadmap, release plan, milestone plan, backlog prioritization, sequencing, what to build next, or to turn improve/ideate/brainstorm/design-discussion outputs into an execution sequence. Not for implementing code or writing PR-level plans.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-structured, actionable instruction skill with a clear phased workflow, validation checkpoints, a quality-bar checklist, and a properly signaled one-level-deep reference to the bundled template; minor conciseness gains are available.

DimensionReasoningScore

Conciseness

Largely lean with terse tables and bullets, but includes some conceptual framing ("A roadmap is direction + prioritization + dependencies...") that slightly over-explains and could be trimmed; not verbose enough to warrant 3.

4 / 5

Actionability

Provides concrete, copy-paste-ready guidance: an explicit candidate-normalization table with defined fields, a precise destination-resolution ordering, prioritization rules, handoff routing, and invocation variants — actionable without code.

5 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints (confidence marking, evidence-gap disclosure, "update in place", a final Quality bar checklist); the destructive/batch cap does not apply to artifact writing.

5 / 5

Progressive Disclosure

Well-sectioned overview with a clearly signaled one-level-deep reference to the real bundle file "assets/roadmap-template.md"; content is appropriately split between the body and the template.

5 / 5

Total

19

/

20

Passed

Description

100%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.

A strong, third-person description that concretely states capabilities, provides comprehensive natural trigger terms, and explicitly answers both what and when while drawing a clear boundary against adjacent planning skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Build evidence-backed software/product roadmaps", "prioritize and sequence work across Now/Next/Later, milestones, dependencies, risks, and handoffs" — giving comprehensive coverage rather than vague domain naming.

5 / 5

Completeness

Explicitly answers both what (build/prioritize/sequence roadmaps) and when ("Use when asked for a roadmap... backlog prioritization, sequencing, what to build next") with concrete trigger phrases, plus an explicit non-scope boundary.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms — "roadmap", "feature roadmap", "technical roadmap", "release plan", "milestone plan", "backlog prioritization", "sequencing", "what to build next" — that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (evidence-backed roadmapping at one altitude above implementation) with distinct Now/Next/Later framing and an explicit "Not for implementing code or writing PR-level plans" boundary minimizing conflict with planning/brainstorm skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
joshuadavidthomas/agent-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.