Generate structured product ideas with hypotheses and cheapest-validation plans from PMContext.
npx skills add https://github.com/Wcof/PMSkill --skill pm-ideation
Please help me install this Agent Skill. Skill: pm-ideation Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-ideation Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-ideation
This Skill helps product teams move beyond vague brainstorming and single-solution thinking by generating a structured set of product ideas from PMContext. It forces ideation across both existing-product optimization and adjacent new-scenario exploration, then ties each idea to a cheapest possible validation path.
Ask the agent to use pm-ideation on the current PMContext to generate at least five optimize and explore ideas with hypotheses, cheapest validations, and a recommended option to test first.
High-intent search queries and answers about installing and using this skill.
To generate testable product ideas, you need an ideation process that transforms product context into hypotheses with explicit assumptions and lowest-cost validation methods. This approach separates ideas into optimize and explore tracks, balancing incremental improvements with new-scenario exploration.
The best way to structure brainstorming for product discovery is using dual-track ideation, forcing separation between optimizing existing features and exploring adjacent scenarios. This method requires generating at least five deduplicated ideas, each tied to a hypothesis and a cheapest possible validation path.
To plan early experiments for new product scenarios, attach a cheapest-validation plan to every generated hypothesis. Compare ideas using a decision matrix covering cost, expected benefit, risk, and validation cycle to recommend the most viable option to test first.
Yes, you can use your current product context for hypothesis-driven ideation if the workflow supports PMContext traceability. This ensures every generated idea connects back to the original context and outputs are suitable for downstream assumption and experiment planning.
To compare optimize versus explore ideas during concept expansion, build a comparison matrix that evaluates cost, expected benefit, risk, and validation cycle. This prevents teams from over-focusing on incremental improvements and recommends what to test first.
WcofDefine a north star metric and input metrics framework from PMContext requirements.
WcofGenerate assumption validation workflows from PMContext with pretotype experiments.
WcofGenerate structured user interview scripts from PMContext for product discovery.
fsollaFacilitate assumption mapping workshops to validate design hypotheses with outcome-based metrics.
