CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-roadmap

Create or update a project roadmap with major milestones. Generates the configured roadmap artifact (default .ai-factory/ROADMAP.md) — a strategic checklist of high-level goals. Use when user says "roadmap", "project plan", "milestones", or "what to build next".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aif-roadmap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-only skill with clear mode routing, concrete templates, and explicit confirmation checkpoints. Its main weaknesses are duplication (the roadmap template and skill-context rules each appear twice) and front-loaded generic policy boilerplate that inflates token cost without adding roadmap-specific value.

Suggestions

Remove the duplicate ROADMAP.md template — keep only the 'ROADMAP.md Format' section (or only Step 1.3) and reference it from the other location.

Consolidate the skill-context loading rules, which currently appear both in 'Shared project skill-context' and again in Step 0, into a single statement of precedence and application rules.

Move the generic 'Runtime-aware questions' delivery policy into a shared reference file (or trim it to 3-4 bullet essentials) so the roadmap-specific workflow starts near the top of the body, and add example Grep/Glob patterns to the codebase-exploration steps.

DimensionReasoningScore

Conciseness

The numbered workflow steps are efficient, but the ROADMAP.md template is duplicated (Step 1.3 and the 'ROADMAP.md Format' section), the skill-context precedence rules are stated twice, and ~30 lines of generic runtime/question policy pad the front of the file.

3 / 5

Actionability

Concrete commands (git log --oneline -20), exact paths, a copy-paste-ready ROADMAP.md template, and fully specified AskUserQuestion option sets make the guidance mostly executable; minor gaps include Grep/Glob steps with no example patterns and the vague 'Explore codebase briefly'.

4 / 5

Workflow Clarity

Mode routing is explicit, each mode has numbered steps, user-confirmation checkpoints are present, and an enforcement step ('If any rule is violated — fix the output before presenting') provides a feedback loop. Minor gaps: Mode 3 is described as automated 'without interactive questions' yet 3.4 depends on confirmation, and no final check verifies the saved file matches the template.

4 / 5

Progressive Disclosure

No bundle files exist so all content is necessarily inline, and headers are well organized, but the generic 'Runtime-aware questions' contract and shared skill-context policy (~30 lines of multi-skill boilerplate) are inlined before the actual roadmap workflow — content that belongs in a shared separate reference.

3 / 5

Total

14

/

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.

A strong description that follows best practice: third-person voice, concrete actions with a named default artifact, and an explicit 'Use when' clause with quoted natural trigger phrases. Its only weaknesses are the missing check-progress capability and slight trigger overlap with the sibling planning skill.

DimensionReasoningScore

Specificity

Concrete actions are named ('Create or update a project roadmap', 'Generates the configured roadmap artifact (default .ai-factory/ROADMAP.md)') including the artifact path, but the check-progress mode from the body is not mentioned, leaving a coverage gap that keeps it below the comprehensive anchor.

4 / 5

Completeness

It clearly answers both what ('Create or update a project roadmap with major milestones... a strategic checklist of high-level goals') and when ('Use when user says "roadmap", "project plan", "milestones", or "what to build next"') with explicit concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Quoted triggers 'roadmap', 'project plan', 'milestones', and 'what to build next' are natural user phrases with good synonym coverage, though common variants like 'strategic plan', 'goals', or 'timeline' are missing.

4 / 5

Distinctiveness Conflict Risk

The roadmap/milestone-checklist niche is mostly distinct with a concrete default artifact path, but the 'project plan' trigger overlaps with the closely related /aif-plan planning skill referenced in the body, creating minor conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-roadmap/SKILL.md

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.