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.
64
75%
Does it follow best practices?
Impact
—
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 strong skill description that clearly communicates what the skill does (multi-perspective product ideation from three specific roles) and when to use it (feature brainstorming, solution ideation, product trio sessions). It uses natural trigger terms, has a well-defined niche, and follows third-person voice conventions.
| 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 context (existing product) are clearly described. | 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'. 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 or general product management skills due to the specific methodology described. | 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 is a moderately well-structured brainstorming skill that provides clear steps and role-based ideation perspectives. Its main weaknesses are the lack of concrete output examples (what a good idea card looks like), unnecessary domain explanations that Claude already knows, and external links that don't serve as actionable references. Adding an example output and trimming the domain context would significantly improve it.
Suggestions
Add a concrete example of a prioritized idea output (name, description, reasoning, assumptions) so Claude knows the expected format and quality bar.
Remove or significantly trim the 'Domain Context' section — Claude already knows about Product Trios, Teresa Torres, and Opportunity Solution Trees.
Replace the 'Further Reading' external links with either bundle files containing relevant frameworks or remove the section entirely, as Claude cannot reliably access these URLs.
Add iteration guidance: what to do if the user wants to refine, combine ideas, or explore a different direction after the initial brainstorm.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary context like explaining what a Product Trio is and quoting Teresa Torres — Claude already knows this. The 'Further Reading' links are not actionable by Claude in most contexts. However, the core instructions are reasonably tight. | 2 / 3 |
Actionability | The skill provides a clear multi-step process with specific criteria for ideation and prioritization, but it's entirely instructional with no concrete examples of what good output looks like (e.g., a sample idea card, expected output format). The guidance is specific enough to follow but lacks a concrete example input/output pair. | 2 / 3 |
Workflow Clarity | The four steps are clearly sequenced and logically ordered, with step 1 including a clarification checkpoint. However, there's no feedback loop — no guidance on what to do if the user disagrees with prioritization, wants to iterate, or if the brainstorm needs refinement. For a discovery-oriented workflow, iteration guidance is important. | 2 / 3 |
Progressive Disclosure | The Further Reading section references external URLs (not bundle files), which Claude cannot reliably access. There are no bundle files to support progressive disclosure. The content is all inline but not excessively long, so it's acceptable for the skill's scope, though the external links add little 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
d384f0c
- 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.