CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-roadmap-next

Recommend the next planning scope from a project's roadmap, accounting for dependencies, active plans and estimated size. Use to choose what to plan next; does not update the roadmap or start planning without the user's selection.

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-next/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 an unusually rigorous, well-sequenced instruction skill: concrete paths, defaults, decision order, explicit stop conditions, and a recheck loop make the workflow highly followable. Its weaknesses are token efficiency and structure — a generic interaction contract is duplicated between the intro and section 5, and all edge-case detail lives inline in a single 180-line file with no reference files.

Suggestions

Move the 'Runtime-aware questions' and 'Shared project skill-context' sections into a shared one-level-deep reference file, keeping a one-line pointer in SKILL.md, to remove ~30 lines of family-wide policy from this skill.

Deduplicate section 5's question-tool rules (plain-text fallback, cancellation-is-not-approval, non-interactive behavior) by referencing the interaction contract once instead of restating it.

Move section 2's inventory edge cases and localized heading-equivalent lists into a reference file, keeping the milestone-inventory steps themselves inline as the overview.

DimensionReasoningScore

Conciseness

The body is dense rule-writing without concept explanations Claude already knows, but the generic interaction contract ("AskUserQuestion and Questions below describe the intended interaction...", "An empty/cancelled response... is not an answer or approval") spans ~21 lines of family-wide policy, and section 5 restates those same rules ("Cancellation, empty replies, preselected options and elapsed time are not approval"). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is above 2 because there is little padding beyond the duplicated policy, and below 4 because the duplication and inline boilerplate are more than minor.

3 / 5

Actionability

Guidance is largely executable for an instruction-only skill: exact paths (".ai-factory/config.yaml", "paths.plans"), concrete defaults ("fast=1, full=2, ultra=3 points"), exact size mapping ("S/M/L/XL = 1/2/3/4+ points"), and a copy-paste-ready output block ("/aif-plan full Add mail personalization helpers..."). It stays at 4 rather than 5 because some direction remains abstract ("a brief targeted code read", "explain the shared module/direct continuation") and only the planning-request portion of the output is exemplified, not a full recommendation with alternatives.

4 / 5

Workflow Clarity

Sections 1–5 form a clear numbered sequence with explicit validation and feedback loops: ordered mode-resolution rules ("If present but invalid, warn and use ultra"), explicit stop conditions ("Missing roadmap → suggest /aif-roadmap and stop"), uncertain-by-default handling ("Ambiguous linkage or task sections leave claim/progress coverage uncertain, never unclaimed by default"), and a post-selection recheck ("After explicit selection, recheck readiness, claims, mode and source revisions"). This matches the 5 anchor's clear sequence, explicit validation steps, and error-recovery paths; nothing significant is missing for a read-only workflow.

5 / 5

Progressive Disclosure

Sections are well organized with clear headers, but the ~180-line body has no bundle files at all, and content that plausibly belongs in separate files is inlined: the generic "Runtime-aware questions" and "Shared project skill-context" policy sections, plus detailed edge-case lists like the localized heading equivalents ("## Задачи", "## Связь с дорожной картой", "Веха:"). This fits 'some structure but could be better organized; content that should be separate is inline'; it is above 2 because structure and navigation are good, and below 4 because SKILL.md carries the full detail load rather than pointing to one-level-deep references.

3 / 5

Total

15

/

20

Passed

Description

75%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, third-person, and clearly communicates a read-only recommendation role with an explicit use case and a well-drawn boundary against actually starting planning. Its main gaps are thin trigger coverage — one 'when' phrase with no synonyms like 'next milestone' or 'what to work on next' — which keeps most dimensions at 4 rather than 5.

Suggestions

Add natural trigger synonyms to broaden matching, e.g. "Use to choose what to plan, work on, or pick as the next milestone from the roadmap".

Expand the 'when' clause with concrete trigger phrases (e.g., "Use when the user asks what to plan or build next") to reach the fully-explicit completeness anchor.

DimensionReasoningScore

Specificity

"Recommend the next planning scope from a project's roadmap, accounting for dependencies, active plans and estimated size" names the domain and several concrete considerations (dependencies, active plans, size estimation), matching the 'several specific actions; minor gaps' anchor. It stays at 4 rather than 5 because the core capability is a single recommend action, not a comprehensive list of distinct operations; it is above 3 because the accounted factors and the exclusion clause are concrete, not generic.

4 / 5

Completeness

The 'what' is clear ("Recommend the next planning scope... accounting for dependencies, active plans and estimated size") and the 'when' is explicit ("Use to choose what to plan next"), so it exceeds the 3 anchor where 'when' is only implied. It does not reach 5 because the when clause provides just one trigger phrase rather than multiple concrete trigger conditions as in the 5 anchor example.

4 / 5

Trigger Term Quality

"roadmap", "planning scope", "plan next" and "what to plan next" are phrases a user would naturally say when needing this skill, fitting the 'good keyword coverage; a few natural terms missing' anchor. It falls short of 5 because common variations like "next milestone", "what to work on next", or "backlog" are absent, and it is clearly above 3 since the present terms are natural rather than jargon.

4 / 5

Distinctiveness Conflict Risk

"Recommend the next planning scope from a project's roadmap" carves a clear niche, and the boundary "does not update the roadmap or start planning without the user's selection" explicitly separates it from sibling roadmap/planning skills, fitting 'mostly distinct; minor overlap risk with closely related skills'. It is not 5 because closely related planning skills do exist and "planning" language retains some overlap risk that the single boundary clause only partially mitigates.

4 / 5

Total

16

/

20

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.

Validation — 15 / 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

lee-to/ai-factory

Path

skills/aif-roadmap-next/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.