mcpField
I
identify-assumptions-existing

identify-assumptions-existing

github.com/phurynProductivity27.5k2.8k installsUpdated 2w ago
Repository

About identify-assumptions-existing

A skill for examining an existing product feature idea from product, design, and engineering perspectives, surfacing assumptions across value, usability, viability, and feasibility. It supports devil's advocate analysis before a feature proceeds, recording confidence and a suggested test for each assumption.

Key features

  1. 01Review ideas from three role perspectives
  2. 02Cover four areas of risk
  3. 03Describe how each assumption could fail
  4. 04Rate confidence in assumptions
  5. 05Suggest ways to test assumptions

Use cases

  1. 01Assess a feature proposal for an existing product
  2. 02Identify usability and adoption barriers
  3. 03Check business support and integration risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-existing

After installing, type/identify-assumptions-existingin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported