CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

user-story-mapping

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

Quality

76%

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 ./plugins/sdlc/skills/user-story-mapping/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.

The body delivers a well-sequenced, concrete facilitation workflow with useful quality checks and pitfalls, and is reasonably actionable as instruction-only guidance. Its weaknesses are redundancy with content Claude already knows, and a broken progressive-disclosure structure: it points to template.md and examples/sample.md that are not present while inlining everything in one long file.

Suggestions

Create the referenced `template.md` and `examples/sample.md` bundle files (or remove the references and keep the inline templates) so readers are not sent to missing files.

Trim the framework background Claude already knows — the Patton 2D-axis explanation, "Why This Works", and the When/When NOT sections largely restate the Purpose and the per-step quality checks.

Add an explicit feedback loop after Step 7 (e.g., 'if gaps are found, return to Step 3 and revise the backbone') and a worked example of release lines in Step 6 to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly actionable template guidance, but includes background Claude already knows (the Patton framework's 2D axes, "Why This Works", "When to Use / When NOT to Use" lists) and duplicates the frontmatter intent verbatim as the Purpose opening. It fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the clearly verbose level-2 anchor, since much of the content is fill-in structure.

3 / 5

Actionability

Concrete fill-in markdown templates for every step, a worked persona example ("Sarah, 35-year-old freelance graphic designer..."), per-step quality checks, and pitfalls with symptom/consequence/fix provide mostly executable guidance. It falls short of fully copy-paste-ready because "Use `template.md` for the full fill-in structure" and "See `examples/sample.md`" point to files that do not exist in the bundle, and no complete worked story map is shown.

4 / 5

Workflow Clarity

Steps 1–7 are clearly numbered and sequenced, with per-step quality checks serving as checkpoints and Step 7 acting as a final review. It misses the level-5 anchor because there is no explicit feedback loop (e.g., 'if gaps are found in Step 7, revisit the activities') and the vertical prioritization step (Step 6) has no worked example of release lines.

4 / 5

Progressive Disclosure

The body references `template.md` and `examples/sample.md`, but no bundle files exist, so those references are dangling; meanwhile a ~310-line monolith inlines the full per-step templates and pitfall catalog that belong in those separate files. This matches 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

78%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 clearly and explicitly states both what the skill does and when to use it, with mostly natural trigger terms and a distinct niche. Its main weakness is that it describes a single action (creating one artifact) rather than a broader set of concrete capabilities, and its workflow/backlog/MVP triggers have some overlap with adjacent planning skills.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "Create a user story map that lays out activities, steps, tasks, and release slices" — enumerating the artifact's components rather than several distinct actions, matching the '1-2 concrete actions, not comprehensive' anchor. It is below the level-4 anchor because it does not list multiple specific capability actions.

3 / 5

Completeness

Explicitly answers both what ("Create a user story map that lays out activities, steps, tasks, and release slices") and when ("Use when planning a workflow, backlog, or MVP around the user journey") with concrete trigger phrases, matching the top anchor. Uses appropriate third-person/infinitive voice throughout.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: "user story map", "planning a workflow", "backlog", "MVP", "user journey". A few common variations are missing ("story mapping", "release planning", "user stories"), so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Distinct niche terms ("user story map", "release slices", "user journey") minimize conflict, but the triggers "planning a workflow, backlog, or MVP" could overlap with roadmap or backlog-management skills — minor overlap risk with closely related skills rather than minimal conflict.

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

whimzyLive/nightshift-ai

Path

plugins/sdlc/skills/user-story-mapping/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.