identify-assumptions-existing Checked
Installation
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "identify-assumptions-existing" skill by following the instructions at https://skill123.me/install/identify-assumptions-existing.
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/identify-assumptions-existing.sh | bash
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 1 KBNot live-tested yet — this skill is rated on static analysis only.
About this skill
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.
Documentation
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
Score breakdown
Assessment methodology
Version history
Imported from phuryn/pm-skills@main
