brainstorm-ideas-new

Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

Quality

69%

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 ./pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md

Quality

Content

50%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 is a clear, sectioned procedure for multi-perspective ideation but stays at a high level: it lacks concrete templates or output examples, validation checkpoints, and local bundle references to deepen the material. It is adequate but not exemplary.

Suggestions

Add a concrete output template or one worked example of a prioritized idea with reasoning so Claude has a copy-paste-ready format.

Trim or relocate the 'Initial Discovery vs Continuous Discovery' contrast since it is background Claude largely already knows, freeing token budget.

Either add a local references file (e.g. examples.md) for deeper material and link to it one level deep, or remove the external-link section if it does not aid execution.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-sectioned, but the 'Initial Discovery vs Continuous Discovery' domain context paragraph explains a concept and contrast that is largely background padding rather than strictly necessary instruction.	3 / 5
Actionability	The steps give clear direction on what to produce (5 ideas per perspective, prioritize top 5, reasoning per idea), but provide no concrete executable examples, templates, or output formats — it reads more as a procedure outline than copy-paste guidance.	3 / 5
Workflow Clarity	Steps are sequenced (understand -> ideate -> prioritize -> detail), but there are no validation checkpoints or feedback loops; since this is an ideation (non-destructive) skill the destructive-cap cap does not apply, yet checkpoints are still absent.	3 / 5
Progressive Disclosure	Has clear section headers and a 'Further Reading' list of external links, but there are no bundle files (references/scripts/assets absent), so the skill is monolithic with external links rather than one-level-deep local references; structure is moderate.	3 / 5
	Total	12 / 20 Passed

Description

73%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 solid description that explicitly answers both what and when with concrete trigger language and natural phrasing. It is slightly less specific in listing concrete actions and has minor distinctiveness overlap with adjacent ideation skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('feature ideas for a new product in initial discovery') and concrete actions ('Brainstorm... generate... from PM, Designer, and Engineer perspectives'), but 'brainstorm' and the three-viewpoint framing are somewhat abstract rather than a list of several distinct concrete actions.	3 / 5
Completeness	Clearly states what it does ('Brainstorm feature ideas... from PM, Designer, and Engineer perspectives') and when to use it ('Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('brainstorm feature ideas', 'product discovery', 'startup idea', 'initial ideation'); missing a few common synonyms but good coverage overall.	4 / 5
Distinctiveness Conflict Risk	The 'new product / initial discovery' framing carves a fairly distinct niche away from continuous-discovery skills; minor overlap risk with general ideation or feature-prioritization skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md
Commit: 8607e3b

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