CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary procedural skill body: lean, rule-dense, fully executable, with a clearly sequenced six-phase workflow, explicit validation and error-recovery paths for every failure mode, and textbook conditional loading of its one bundle reference. Nothing teaches concepts Claude already knows, and every instruction is copy-paste concrete down to the exact report and reply formats.

DimensionReasoningScore

Conciseness

The body is telegraphic, rule-dense prose ('Exit 3 means a file was not found', 'A `?` is not a marker: a formula like `crit ? 2 : 1` passes') with zero concept-teaching — it never explains what an ADR, sprint, or QA gate is — so every token earns its place and it assumes Claude's competence.

5 / 5

Actionability

Fully executable throughout: copy-paste commands ('bash .claude/scripts/story-facts.sh --lint --granularity <story_granularity> [--sprint | --all | <path> ...]', 'bash .claude/scripts/adr-status.sh'), exact report templates, exact fix texts for each failure mode, and exact fallback strings ('no sprint plan found').

5 / 5

Workflow Clarity

Six explicitly sequenced phases with validation checkpoints everywhere: exit-code and NOT_FOUND row handling, an empty-scope stop guard ('Never print a `Ready: 0 / Needs Work: 0` summary over an empty list'), a verdict-precedence ladder, and a gate-override flow with 'Never a silent READY'. The skill is read-only, so the destructive/batch cap does not apply, and batch-scope validation is present anyway.

5 / 5

Progressive Disclosure

The single bundle reference (references/qa-lead-gate.md, verified to exist) is cited one level deep in Phase 5 with explicit conditional loading ('On a skip, do not load it'), and everything kept inline is needed on every run; clear phase sections and tables make navigation easy.

5 / 5

Total

20

/

20

Passed

Description

87%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: it states concrete readiness checks in third person and pairs them with an explicit, natural 'Use when' trigger clause covering story, sprint, and build/start phrasing. Its only weakness is coverage — the body checks more (assets, estimates, test evidence, manifest) than the description advertises, and a few natural trigger variants are missing.

DimensionReasoningScore

Specificity

Names four concrete check areas ('clear acceptance criteria, no open questions, valid ADR and dependencies'), but omits coverage the skill actually performs (asset references, estimates, test evidence, manifest rules), matching 'several specific actions; minor gaps in coverage' rather than comprehensive.

4 / 5

Completeness

Explicitly answers both questions: the what ('Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies') and the when ('Use when the user asks if a story, or the sprint's stories, are ready to start or build') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'ready to start or build', 'story', and 'the sprint's stories' (plus 'ready to implement' in the what-clause) give good synonym coverage, but common variations such as 'ready for dev' or 'begin implementation' are absent, fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'story', 'ADR', 'acceptance criteria', and 'sprint' carve a clear agile story-readiness niche with distinct triggers and minimal overlap risk with other skills; voice is third person ('Checks'), so no penalty applies.

5 / 5

Total

18

/

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

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/story-readiness/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.