identify-assumptions-existing
Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility. Uses multi-perspective devil's advocate thinking. Use when stress-testing a feature idea, doing risk assessment, or preparing for assumption mapping.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install phuryn-pm-skills-identify-assumptions-existing
Repository
Skill path: pm-product-discovery/skills/identify-assumptions-existing
Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility. Uses multi-perspective devil's advocate thinking. Use when stress-testing a feature idea, doing risk assessment, or preparing for assumption mapping.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: phuryn.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install identify-assumptions-existing into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/phuryn/pm-skills before adding identify-assumptions-existing to shared team environments
- Use identify-assumptions-existing for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: identify-assumptions-existing description: "Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility. Uses multi-perspective devil's advocate thinking. Use when stress-testing a feature idea, doing risk assessment, or preparing for assumption mapping." --- ## Identify Assumptions (Existing Product) Devil's advocate analysis to surface risky assumptions across four risk areas. ### Context You are stress-testing a feature idea for **$ARGUMENTS**. If the user provides files (designs, PRDs, research), read them first. ### Instructions The user will describe their product, objective, market segment, and feature idea. Work through these steps: 1. **Think from three perspectives** about why this feature might fail: - **Product Manager perspective**: Business viability, market fit, strategic alignment - **Designer perspective**: Usability, user experience, adoption barriers - **Engineer perspective**: Technical feasibility, performance, integration challenges 2. **Identify assumptions across four risk areas**: - **Value**: Will it create value for customers? Does it solve a real problem? - **Usability**: Will users figure out how to use it? Is the learning curve acceptable? - **Viability**: Can marketing, sales, finance, and legal support it? - **Feasibility**: Can it be built with existing technology? Are there integration risks? 3. **For each assumption**, note: - What specifically could go wrong - How confident you are (High/Medium/Low) - Suggested way to test it Think step by step. Be thorough but constructive — the goal is to strengthen the idea, not kill it. --- ### Further Reading - [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas) - [How to Manage Risks as a Product Manager](https://www.productcompass.pm/p/how-to-manage-risks-as-a-product-manager) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)