CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured, actionable guidance with a clear sequenced workflow and concrete fill-in templates, but it is padded with conceptual explanation Claude already knows and points to bundle files (template.md, examples/sample.md) that do not exist.

Suggestions

Trim the "Why This Works", "Anti-Patterns (What This Is NOT)", and "When to/NOT to Use This" sections to essentials — Claude already understands story mapping, so keep only what changes its behavior.

Create the referenced `template.md` and `examples/sample.md` (or remove the references) so progressive disclosure points to real files; move the fill-in markdown blocks into template.md to slim SKILL.md into an overview.

Consider relocating the per-step quality checks into the template rather than the overview body to reduce token weight in the always-loaded file.

DimensionReasoningScore

Conciseness

The body spends tokens explaining concepts Claude already knows ("Invented by Jeff Patton, story mapping organizes work into a 2D structure", the "Why This Works", "Anti-Patterns", and "When (Not) to Use" sections), so it is mostly efficient but padded with unnecessary conceptual explanation.

2 / 3

Actionability

Each step ships a copy-paste-ready fill-in markdown template with concrete examples (a named persona, sample activities, sample tasks), giving fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

A clear seven-step sequence (Context → Narrative → Activities → Steps → Tasks → Prioritize → Gaps) with per-step "Quality checks" acting as checklists and a closing gap-review step; this is a planning artifact, not a destructive/batch operation, so no validate-retry loop is required.

3 / 3

Progressive Disclosure

The body signals references to `template.md` and `examples/sample.md`, but neither file (nor any references/scripts/assets/examples directory) exists in the bundle, so the references are broken and the fill-in template content stays inline in SKILL.md rather than being split out.

2 / 3

Total

10

/

12

Passed

Description

100%

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, concise description that states concrete capabilities and an explicit Use-when trigger using natural terminology. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists several concrete outputs — "lays out activities, steps, tasks, and release slices" — matching the score-3 anchor of multiple specific concrete actions rather than vague language.

3 / 3

Completeness

It 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 an explicit Use-when trigger.

3 / 3

Trigger Term Quality

Natural trigger terms a user would say are present — "workflow", "backlog", "MVP", "user story map", "user journey" — giving good coverage of the phrasing a planner actually uses.

3 / 3

Distinctiveness Conflict Risk

The story-map framing (activities/steps/tasks/release slices, user journey) carves a clear niche unlikely to trigger for the wrong skill; the broad "workflow/backlog/MVP" terms are anchored by the distinctive story-mapping verb.

3 / 3

Total

12

/

12

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.

Validation15 / 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
deanpeters/Product-Manager-Skills
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.