SkillAgentSearch 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

Install / Use

npx skills add phuryn/pm-skills --skill identify-assumptions-existing

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

77/100

Supported Platforms

Universal

Our assessment of identify-assumptions-existing

identify-assumptions-existing scores 77/100 on our quality scale, 92nd of 127 Education & Research skills we index.

Its SKILL.md is 2.1 KB long, split into 4 sections and no code examples: moderately detailed.

With 26,568 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
20/30
Structure
8/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 11 days ago, so identify-assumptions-existing is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

identify-assumptions-existing compared with similar skills

All 4 of these similar skills score higher than identify-assumptions-existing; compare them before choosing.

SkillScoreStarsUpdatedFormat
identify-assumptions-existing (this skill)by phuryn7726.6k11d agoSKILL.md
last30days-skillby mvanhorn10062.8k2d agoCLAUDE.md
algorithmic-artby anthropics100177.9k3d agoSKILL.md
pptxby anthropics100177.9k3d agoSKILL.md
designby nextlevelbuilder100130.2k4d agoSKILL.md

Frequently asked questions

How do I install identify-assumptions-existing?
Run npx skills add phuryn/pm-skills --skill identify-assumptions-existing. The install tabs above show the steps for each supported agent.
Which AI agents does identify-assumptions-existing work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is identify-assumptions-existing safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is identify-assumptions-existing still maintained?
The repository was last updated 11 days ago, so identify-assumptions-existing is actively maintained.

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

Related Skills

View on GitHub
GitHub Stars26.6k
CategoryEducation
Updated11d ago
Forks2.8k

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions