identify-assumptions-existing

Identify risky assumptions for a feature idea across Value, Usability, Viability, and Feasibility.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-kit --skill identify-assumptions-existing-officebeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identify-assumptions-existing
Source: https://github.com/officebeats/beats-pm-kit/tree/main/.agent/skills/identify-assumptions-existing
Command: npx skills add https://github.com/officebeats/beats-pm-kit --skill identify-assumptions-existing-officebeats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potential risks and hidden assumptions associated with a new feature idea for an existing product, preventing costly mistakes and ensuring better product-market fit.

Core Features & Use Cases

  • Assumption Identification: Surfaces assumptions across Value, Usability, Viability, and Feasibility.
  • Risk Assessment: Evaluates the potential downsides of each assumption.
  • Testing Suggestions: Provides actionable ideas for validating assumptions.
  • Use Case: Before launching a new feature, use this Skill to perform a devil's advocate analysis and uncover potential pitfalls from product, design, and engineering viewpoints.

Quick Start

Use the identify-assumptions-existing skill to identify risky assumptions for the new 'user profile customization' feature.

Frequently Asked Questions about identify-assumptions-existing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify risky assumptions for a new feature idea in an existing product?

To identify risky assumptions for a new feature, stress-test the idea across Value, Usability, Viability, and Feasibility dimensions using multi-perspective devil's advocate thinking. This surfaces hidden risks and potential pitfalls from product, design, and engineering viewpoints.

What is assumption mapping and how does it help with feature validation?

Assumption mapping is a risk assessment process that evaluates potential downsides across product, design, and engineering dimensions. It helps with feature validation by surfacing hidden pitfalls and providing actionable ideas to test product-market fit before launch.

When do I need to perform a devil's advocate analysis on product features?

You need to perform a devil's advocate analysis on product features before launching a new feature idea. This stress-testing process uncovers potential risks and hidden assumptions across Value, Usability, Viability, and Feasibility to prevent costly mistakes.

What product information do I need to provide for a comprehensive risk assessment?

For a comprehensive risk assessment, you need to provide input describing the existing product, objective, market segment, and feature idea. This context enables multi-perspective analysis across Value, Usability, Viability, and Feasibility dimensions.

What's the best way to stress-test feature ideation for potential viability and feasibility risks?

The best way to stress-test feature ideation is by employing multi-perspective devil's advocate thinking across Value, Usability, Viability, and Feasibility dimensions. This evaluates potential downsides and provides actionable validation testing suggestions.

Does this risk assessment approach work for any feature idea within an existing product?

Yes, this risk assessment approach works for any feature idea within an existing product. It requires user input describing the product, objective, market segment, and feature idea to perform comprehensive assumption mapping and stress-test risks.