brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
80
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.mdQuality
Discovery
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.
This is a well-crafted skill description that clearly communicates its purpose, methodology, and trigger conditions. It uses third person voice, includes an explicit 'Use when...' clause with multiple trigger scenarios, and carves out a distinct niche around product trio ideation. The description is concise yet comprehensive, covering both the what and when effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: brainstorming product ideas, multi-perspective ideation from PM/Designer/Engineer viewpoints. The methodology (product trio, multi-perspective) and scope (existing product, new features) are clearly articulated. | 3 / 3 |
Completeness | Clearly answers both what ('Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints') and when ('Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'brainstorm', 'product ideas', 'feature ideas', 'ideating', 'product trio', 'PM', 'Designer', 'Engineer', 'solutions', 'opportunity'. These cover common variations of how users would phrase such requests. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of product ideation, multi-perspective (PM/Designer/Engineer), and product trio framing creates a clear niche. It's distinct from generic brainstorming skills due to the specific methodology and role-based viewpoints. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for multi-perspective product ideation with clear role-based perspectives and prioritization criteria. However, it lacks concrete output examples, includes unnecessary domain explanations Claude already knows, and misses validation checkpoints in what is inherently a collaborative, iterative workflow. The external reading links add little practical value for Claude's execution.
Suggestions
Add a concrete example of one prioritized idea (name, description, reasoning, assumptions) to anchor the expected output format and quality.
Remove or significantly trim the Domain Context section — Claude already knows about Product Trios, Teresa Torres, and Opportunity Solution Trees.
Add an explicit checkpoint after ideation (e.g., 'Present the 15 ideas and ask the user which direction resonates before prioritizing') to create a feedback loop in this collaborative workflow.
Replace external Further Reading links with a note that these concepts are well-known, or move them to a separate reference file if they must be retained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary context like explaining what a Product Trio is and quoting Teresa Torres — Claude already knows this. The 'Further Reading' links are also of questionable value since they're external URLs Claude can't necessarily access or use. The Domain Context section could be trimmed significantly. | 2 / 3 |
Actionability | The instructions provide a clear multi-step process with specific perspectives and prioritization criteria, but the guidance remains at the level of abstract instruction rather than concrete examples. There are no example outputs showing what a good brainstorm result looks like (e.g., a sample idea card with name, description, reasoning, and assumptions). This makes it harder to ensure consistent, high-quality output. | 2 / 3 |
Workflow Clarity | The four steps are clearly sequenced and logically ordered, but there's no validation or feedback loop. Step 1 mentions asking for clarification, which is good, but there's no checkpoint after ideation (e.g., 'confirm with user before prioritizing') or after prioritization (e.g., 'ask user to select ideas for deeper exploration'). For a collaborative discovery process, missing these interaction checkpoints is a gap. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the 'Further Reading' links point to external URLs rather than local reference files, making them unreliable for Claude. The skill is a single file with no references to supplementary local files. For its length (~50 lines), this is acceptable, but the external links add clutter without reliable value. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- phuryn/pm-skills
- Commit
36ccefd
- 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.