user-story-mapping-workshop

Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/user-story-mapping-workshop/SKILL.md

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.

A highly actionable, well-sequenced workshop protocol that is held back by verbosity and weak progressive disclosure. Conceptual padding duplicates known material and the frontmatter intent, while a referenced template.md is missing from the bundle and bulk content that belongs in it is inlined.

Suggestions

Trim the Key Concepts, Why This Works, Anti-Patterns, and Common Pitfalls sections to the non-obvious essentials (or move them into a reference file) and remove the Purpose section that duplicates the frontmatter intent verbatim.

Either ship the referenced template.md containing the facilitation agenda and output checklist, or remove the dangling 'Use template.md' reference and keep that content inline under a clearly signaled section.

Make the per-question approval gates explicit validate-fix-retry loops (e.g., 'If the user requests changes, regenerate the backbone and re-confirm before proceeding to Q4') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the Purpose section duplicates the frontmatter intent verbatim, and Key Concepts / Why This Works / Anti-Patterns / five Common Pitfalls explain standard Patton story-mapping concepts Claude already knows, with the pitfalls largely restating the anti-patterns.	2 / 5
Actionability	Fully executable facilitation protocol: exact agent prompts per question, 3-4 enumerated options with concrete examples, ASCII backbone/task trees, a full release-slice example, and a copy-paste-ready markdown output template.	5 / 5
Workflow Clarity	Clear sequence (Step 0 -> Q1-Q5 -> Output) with per-question approval gates ('User response: [Approve, modify, or add custom...]'), but error-recovery feedback loops are implicit rather than explicitly framed as validate-fix-retry.	4 / 5
Progressive Disclosure	The file is well-sectioned internally, but the body tells the reader to 'Use template.md for the facilitation agenda and outputs checklist' while no template.md exists in the bundle, and the full output template, examples, and pitfalls are inlined rather than split into that referenced file.	3 / 5
	Total	14 / 20 Passed

Description

83%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, third-person description that clearly answers both what the skill does and when to trigger it, with concrete domain-specific outputs. It is specific and well-targeted, with only minor gaps in trigger synonym coverage and slight overlap risk with related story skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('user story mapping workshop') and several concrete actions/outputs ('adaptive questions', 'structured map output', 'backbone activities, tasks, and release slices'), but the action list is not fully comprehensive.	4 / 5
Completeness	Explicitly states what it does ('Run a user story mapping workshop with adaptive questions and a structured map output') and when to use it ('Use when you need backbone activities, tasks, and release slices for a workflow') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'user story mapping', 'backbone activities', 'release slices', and 'workflow' are natural PM phrases, but common synonyms like 'story map' (singular), 'MVP', or 'release plan' are missing.	4 / 5
Distinctiveness Conflict Risk	'user story mapping workshop' is a clear niche with distinct triggers, but there is minor overlap risk with sibling skills like user-story-mapping and user-story referenced in the body.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/user-story-mapping-workshop/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.