AutoGineer
Generated banner for Identify Assumptions Existing
Generated logo for Identify Assumptions Existing

Identify Assumptions Existing

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Research and analysis
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to evaluating feature ideas for existing products by adopting multiple professional perspectives. By simulating the viewpoints of a Product Manager, Designer, and Engineer, the agent surfaces potential failure points across Value, Usability, Viability, and Feasibility. It is designed to help teams identify hidden risks early, assess their confidence levels, and determine actionable testing strategies to validate or invalidate assumptions before full-scale development.

What it does

  • Analyzes feature ideas from the perspectives of product management, design, and engineering.
  • Categorizes potential risks into Value, Usability, Viability, and Feasibility domains.
  • Evaluates the specific ways a feature might fail to meet its objectives.
  • Assigns confidence levels to identified assumptions to help prioritize risk mitigation.
  • Suggests specific testing methods to validate assumptions.
  • Integrates with provided project documentation like PRDs or design files.

When to use it

  • When stress-testing a new feature idea before committing development resources.
  • During the risk assessment phase of product discovery.
  • When preparing for an assumption mapping workshop.
  • When you need a critical, multi-perspective review of a proposed product change.

Advantages

  • Encourages a comprehensive view by forcing consideration of business, design, and technical constraints.
  • Helps teams move from subjective opinions to evidence-based validation.
  • Provides a constructive framework for identifying weaknesses without discouraging innovation.
  • Facilitates better preparation for product discovery and testing cycles.

Usage examples

“I want to add an AI-powered summary feature to our existing CRM. Can you help me identify the risks?”
The agent will analyze the CRM feature from PM, design, and engineering perspectives, listing assumptions regarding user value, UI complexity, technical feasibility, and business viability.
“Here is my PRD for a new mobile checkout flow. Please perform a devil's advocate analysis.”
The agent will review the provided document and highlight specific risks related to user adoption, technical integration, and business alignment, suggesting ways to test these assumptions.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/identify-assumptions-existing/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip identify-assumptions-existing.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

SKILL.md

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

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-product-discovery/skills/identify-assumptions-existing · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download identify-assumptions-existing.zip