CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

63

Quality

75%

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

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 multi-mode workflow with concrete templates, commands, and confirmation checkpoints. Its main weakness is redundancy in the skill-context enforcement guidance and a duplicated ROADMAP.md format block that inflate token usage.

Suggestions

Collapse the repeated skill-context precedence rules (lines 42-60) into a single concise statement of the override-and-enforce rule rather than restating it as MANDATORY, CRITICAL, 'rule wins', and 'Do NOT ignore'.

Remove the standalone 'ROADMAP.md Format' section (lines 285-303) since the same template already appears in Step 1.3, or replace the inline copy with a one-line pointer to the canonical section.

Trim redundant phrasing in the Critical Rules list where items restate guidance already covered in the mode workflows (e.g., the ownership boundary and no-implementation rules).

DimensionReasoningScore

Conciseness

Mostly efficient but the skill-context section restates the precedence rule multiple times ('MANDATORY', 'CRITICAL', 'rule wins', 'Do NOT ignore') and the ROADMAP.md format is duplicated in both Mode 1 and the standalone 'ROADMAP.md Format' section, so it could be tightened.

3 / 5

Actionability

Provides concrete AskUserQuestion templates with numbered options, explicit commands like 'git log --oneline -20', and a copy-paste-ready roadmap template with only minor gaps.

4 / 5

Workflow Clarity

Clearly sequenced Step 0 to Step 1 with Mode 1/2/3 sub-steps and explicit confirmation checkpoints ('Never remove milestones silently — always confirm'), with only minor validation gaps.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear section headers and no nested references; all content is appropriately inline for this skill type given there are no bundle files, with minor organization gaps from the duplicated format block.

4 / 5

Total

15

/

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, uses third person, and answers both what the skill does and when to use it with explicit natural trigger phrases. It is strong overall, with only minor room to expand trigger-term synonyms and action coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Create or update a project roadmap', 'Generates the configured roadmap artifact', 'strategic checklist of high-level goals') with only minor coverage gaps, sitting above the midpoint but not fully comprehensive.

4 / 5

Completeness

Clearly answers 'what' (create/update roadmap, generate artifact) and explicitly provides 'when' via an explicit 'Use when' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('roadmap', 'project plan', 'milestones', 'what to build next') with good coverage, though a few common synonyms or variants are missing.

4 / 5

Distinctiveness Conflict Risk

Has a clear roadmap-planning niche with distinct triggers, with only minor overlap risk against closely related planning skills like /aif-plan.

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.

Validation14 / 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
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.