Individual skill
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.
pm-product-discovery/skills/identify-assumptions-existing/SKILL.md
Source commit 2a12295a7717569baa7be181b4cfebe3ca38a6bb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27,815
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skill-repository Repository topic
- product-management Repository topic
- agent-skills Repository topic
- agentic-skills Repository topic
- claude-code-marketplace Repository topic
- claude-code-plugins Repository topic
- claude-cowork-plugin Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,102 bytes
Read excerpt
## 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: