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

76%

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

70%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 well-sequenced workflow with strong validation checkpoints and concrete per-step guidance, but it is notably verbose for a context-budgeted skill and points to bundle files (template.md, examples/sample.md) that do not exist.

Suggestions

Remove the verbatim Purpose block that repeats the frontmatter description, and cut the 'Key Concepts' / 'Why This Works' / 'Anti-Patterns' explanatory sections that restate what product strategy is — Claude already knows this.

Delete or replace the ASCII end-to-end summary tree, which duplicates the per-phase detail already given above; if a compact overview is needed, keep only the timeline skeleton.

Either provide the referenced `template.md` and `examples/sample.md` bundle files or remove the references, so the skill does not point users to missing materials.

Dimension	Reasoning	Score
Conciseness	The per-phase tables (Use/Participants/Duration/Output) are tight, but the body pads with a verbatim repeat of the description under Purpose, a 'Key Concepts' section explaining what a strategy session is, and an ASCII end-to-end summary that duplicates the phase list already detailed above.	3 / 5
Actionability	Each step names a concrete skill file, participants, duration, and expected output, and decision points give explicit If YES/If NO branches; as an orchestration/instruction skill the guidance is concrete and executable with only minor gaps.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with explicit validation checkpoints (Decision Points 1-3) and feedback loops (If NO → run discovery, +1 week; If YES high uncertainty → run experiments), matching the explicit-validation-with-recovery anchor.	5 / 5
Progressive Disclosure	Section structure exists and references are signaled one level deep, but the body references its own bundle files (`template.md`, `examples/sample.md`) that are not present in the bundle, and a large amount of phase detail plus a duplicate ASCII summary is inlined rather than split out.	3 / 5
	Total	15 / 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 description that clearly states what the skill does and when to use it, with concrete sub-domain anchors and a natural 'Use when' trigger. It is concise, third-person imperative in form, and largely free of fluff.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete sub-areas ('positioning, discovery, and roadmap planning') as the actions the session covers, with only minor coverage gaps; not a level-5 comprehensive action list but well above naming the domain alone.	4 / 5
Completeness	Explicitly answers both what ('Run an end-to-end product strategy session across positioning, discovery, and roadmap planning') and when ('Use when a team needs validated direction before committing to execution') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural terms a PM or leader would actually say ('product strategy session', 'positioning', 'discovery', 'roadmap planning', 'validated direction') with good coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	'product strategy session' with positioning/discovery/roadmap framing carves a clear niche with distinct triggers; minor overlap risk with adjacent strategy or roadmap skills keeps it just below 5.	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/product-strategy-session/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.