CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

backlog

To validate story readiness for a sprint or to break work into a human WBS.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./instructions/r3/core/skills/backlog/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 disciplined, token-efficient router: terse imperative guidance, a clear mode-classification table with fallbacks, and explicit validation and approval checkpoints, all deferring detail to bundle files that verifiably exist. The main weaknesses are undefined external dependencies (Rosetta prep, load-context, orchestration/hitl skills) and one incomprehensible pitfall line, plus second-level file references that keep progressive disclosure just short of excellent.

Suggestions

Define or point to the external dependencies once — "Rosetta prep steps", the "load-context" skill, and the `orchestration`/`hitl` skills / `engineer` subagent — so the router's instructions are resolvable from the skill bundle.

Rewrite the garbled pitfall "Following literally/mechanically as in 20% cases the problem does exist, but completely the opposite" into a concrete, checkable failure mode.

Surface the second-level files (story-validator-backlog-writeback.md, work-breakdown-templates.md) from the top level, or note in the mode table that each mode file pulls in its own sub-files, so all bundle content is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is composed of short imperative lines with no padding and no explanations of concepts Claude already knows ("Professionally direct. Short lines. No hedging adjectives."), assuming the reader's competence throughout. Every section carries operative instructions, matching the 'lean and efficient; every token earns its place' anchor; the one garbled pitfall line is a clarity defect, not verbosity, so it does not lower this dimension.

5 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a trigger table mapping each mode to a specific asset file, enumerated valid dispatch names with a stop condition, explicit citation formats ("file:line, a verbatim quote, or a named source-of-record field"), and per-write approval gates. It stops short of anchor 5 because external dependencies — "Rosetta prep steps", the "load-context" skill, and the `orchestration`/`hitl` skills and `engineer` subagent — are invoked without any definition or pointer, leaving gaps the reader cannot resolve from the bundle.

4 / 5

Workflow Clarity

The router sequence is clear: classify once and state the mode, run the chosen mode end to end via its asset file, hold gates in-context, with explicit fallbacks (unknown dispatch -> STOP and report; mode unclear -> ask one question naming both modes) and a validation checklist covering verdicts, citations, and approvals. Batch-prone tracker writes have explicit validation ("Every tracker write was individually approved"), so no cap applies, but the detailed step sequencing is delegated to the asset files rather than present here — anchor 4's 'most checkpoints present' rather than anchor 5's fully explicit sequence with feedback loops.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview that routes to real bundle files: every referenced target (story-validator.md, work-breakdown.md, both analysis dispatch files) exists in assets/, and references are consistently signaled with APPLY/READ SKILL FILE directives. It falls short of the one-level-deep anchor 5 because the write-back and templates files are reachable only through the mode files (two levels from the top), and the body gives no listing or hint of those second-level files.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, fairly distinct capability in the agile backlog niche, but it reads as a purpose statement rather than a trigger-equipped skill description. It lacks an explicit 'Use when...' clause and natural trigger vocabulary, capping completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when validating whether a backlog story is ready for a sprint, or when breaking approved work into a WBS."

Include natural user phrasings and synonyms such as "backlog", "grooming", "refinement", "epic", or "decompose" so the description matches how users actually ask.

Spell out "WBS" once ("work breakdown structure (WBS)") or pair it with a plainer verb like "decompose approved work into a human-readable WBS".

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "validate story readiness for a sprint" and "break work into a human WBS" — which matches the anchor for 1-2 concrete actions without comprehensive coverage. It falls short of anchor 4 because only two actions are listed and one is expressed in jargon ("human WBS") rather than plain capability language.

3 / 5

Completeness

The 'what' is clear (validate story readiness, break work into a WBS) but there is no 'Use when...' clause or equivalent explicit trigger guidance — the "To validate... or to break..." purpose phrasing only weakly implies when, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords like "story", "readiness", "sprint", and "WBS" appear, but common natural variations a user would say — "backlog", "grooming", "refinement", "epic", "decompose" — are missing, and "WBS" is technical jargon users may not naturally voice. This fits the 'some relevant keywords but missing common variations or synonyms' anchor rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

Sprint/story-readiness validation and WBS breakdown form a fairly clear niche with distinct trigger territory, with only minor overlap risk against generic planning or project-management skills. It does not reach anchor 5 because the trigger phrasing is not distinctive enough to make conflict risk minimal.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

griddynamics/rosetta

Path

instructions/r3/core/skills/backlog/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.