product-strategy-session

Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/product-strategy-session/SKILL.md

Quality

Content

62%

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

The workflow is sequenced with strong explicit decision-point validation, but the body is verbose with significant restatement, and its actionability and progressive disclosure are undercut because the files it delegates to (template.md, examples/sample.md, and the component skills) are not present in the bundle.

Suggestions

Remove redundancy: drop the verbatim Purpose repeat, fold the ASCII end-to-end summary into a pointer rather than re-listing every phase, and consolidate the Related Skills section instead of re-listing per-phase skills.

Add the referenced bundle files (template.md, examples/sample.md) or replace the file pointers with concise inline guidance so the skill is self-contained and actionable.

Trim conceptual framing sections (Why This Works, Anti-Patterns, When to Use) to the minimum that adds what a competent PM-facing agent would not already know.

Dimension	Reasoning	Score
Conciseness	The body is accurate and structured but padded: the Purpose paragraph repeats the frontmatter intent verbatim, the ASCII end-to-end summary restates every phase, and the Related Skills section re-lists skills already named per phase, plus conceptual framing sections a competent agent largely knows—matching mostly-efficient-but-could-be-tightened.	2 / 3
Actionability	Each activity gives concrete props (participants, duration, output) but the executable mechanism is delegation ("Use: skills/.../SKILL.md") and referenced files like template.md, examples/sample.md, and the skills/ paths do not exist in the bundle, so guidance is concrete but not self-contained or copy-paste ready.	2 / 3
Workflow Clarity	Six numbered phases each have a goal, ordered activities, and explicit Decision Points with YES/NO branches and time impacts that act as validation/feedback gates, matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	References are one-level-deep and signaled, but promised files (template.md, examples/sample.md) and the skills/ paths are absent from the bundle, and the overview keeps all phase detail inline rather than splitting it out—matching some-structure-but-not-fully-realized.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 well-formed description that clearly answers both what the skill does and when to use it, with a distinct strategic niche and third-person voice. The only weakness is trigger-term breadth, which leans on abstract strategic phrasing rather than the concrete vocabulary users naturally say.

Suggestions

Broaden the 'Use when' clause with natural user phrasings such as 'product strategy,' 'roadmap planning,' 'positioning,' or 'product discovery' so it matches how teams actually describe the need.

Consider naming the deliverables explicitly in the what-clause (e.g., 'produces positioning, problem statements, and a prioritized roadmap') to sharpen specificity beyond activity areas.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions across distinct areas: "positioning, discovery, and roadmap planning," matching the multiple-specific-actions anchor rather than the domain-and-some-actions anchor.	3 / 3
Completeness	Explicitly states both what it does ("Run an end-to-end product strategy session across positioning, discovery, and roadmap planning") and when to use it ("Use when a team needs validated direction before committing to execution"), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Has relevant strategic keywords ("product strategy session," "validated direction") but leans abstract and misses common user-phrased variations like "roadmap," "positioning," or "product discovery," matching the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The product-strategy-session niche with its validated-direction trigger is clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-distinct-trigger anchor.	3 / 3
	Total	11 / 12 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/product-strategy-session/SKILL.md
Commit: 9971018

Reviewed: 3 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.