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.
62
72%
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-new/SKILL.mdQuality
Discovery
82%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 solid description that clearly communicates both what the skill does and when to use it, with good natural trigger terms. Its main weakness is that the capability description is somewhat thin — 'brainstorm feature ideas' is a single action rather than a list of concrete outputs or activities. The distinctiveness could also be improved by more clearly differentiating from general brainstorming or product management skills.
Suggestions
Add more specific concrete actions beyond 'brainstorm feature ideas', such as 'generate feature lists, map features to user needs, evaluate feasibility across disciplines, create prioritized feature matrices'.
Strengthen distinctiveness by emphasizing the unique multi-perspective structured output format, e.g., 'Produces structured ideation output organized by PM (user value), Designer (UX), and Engineer (technical feasibility) lenses'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (product discovery/ideation) and mentions the multi-perspective approach (PM, Designer, Engineer), but the core action is essentially just 'brainstorm feature ideas' — it doesn't list multiple concrete actions like generating user stories, prioritizing features, creating feature matrices, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (brainstorm feature ideas from PM, Designer, and Engineer perspectives) and 'when' (explicit 'Use when' clause covering product discovery, startup feature exploration, and initial ideation). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'brainstorm', 'feature ideas', 'new product', 'product discovery', 'startup idea', 'ideation'. These are terms a user would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | The multi-perspective angle (PM, Designer, Engineer) adds some distinctiveness, but 'brainstorm feature ideas' could overlap with general brainstorming skills, product management skills, or ideation tools. The scope is somewhat specific to early-stage discovery but not sharply delineated. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured brainstorming skill with a clear workflow, but it lacks concrete examples of expected output (e.g., a sample feature idea with reasoning and assumptions). The domain context section adds tokens explaining concepts Claude already understands, and the skill would benefit from a sample output template to make the guidance more actionable.
Suggestions
Add a concrete example of one prioritized feature idea with reasoning and assumptions to test, so Claude knows the expected output format and depth.
Remove or significantly trim the 'Domain Context' section — the distinction between initial and continuous discovery can be conveyed in one sentence rather than a full subsection.
Include a sample markdown output template or structure showing what the saved document should look like, since the skill instructs Claude to save output as markdown.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Domain Context' section explaining Initial vs Continuous Discovery is somewhat unnecessary — Claude can understand this distinction without explicit explanation. The rest is reasonably efficient but could be tightened. | 2 / 3 |
Actionability | The instructions provide a clear multi-step process with specific perspectives and criteria, but remain at the level of abstract guidance rather than concrete examples. No sample output format, no example feature idea, no template for how prioritized ideas should look. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced and logical: understand → ideate → prioritize → detail assumptions. For a brainstorming/ideation skill (non-destructive), this level of clarity is sufficient and the steps are unambiguous. | 3 / 3 |
Progressive Disclosure | The 'Further Reading' section provides external references, but these are external URLs rather than companion files. The skill is relatively short and doesn't need file splitting, but the inline domain context section could have been omitted or linked out, and there's no example output file referenced despite the instruction to 'save substantial output as a markdown document.' | 2 / 3 |
Total | 9 / 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
020ee82
- 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.