Skip to content
cccskills
FreePublished on GitHub

identify-assumptions-new

Identify untested assumptions behind a new product idea across eight areas, including customer value, usability, business viability, technology, ethics, market launch, strategy, and team. Rate confidence in each assumption and suggest a test, producing a Markdown analysis.

OriginalShow the original description

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.

See how to install

Good for

  • Checking assumptions behind a new product concept
  • Reviewing launch channels and messaging assumptions
  • Examining technical and team risks together
  • Choosing tests for uncertain assumptions

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Identify Assumptions (New Product)

Comprehensive risk identification across 8 categories — extending the 4 core product risks (Teresa Torres, Continuous Discovery Habits) with Ethics, Go-to-Market, Strategy & Objectives, and Team risks that are critical for new products.

Context

You are evaluating assumptions for a new product: $ARGUMENTS.

If the user provides files (business plans, research), read them first.

Domain Context

The 4 core product risks (Teresa Torres, Continuous Discovery Habits): Value, Usability, Viability, Feasibility.

For new products, extend to 8 risk categories. Good teams assume at least three-quarters of their ideas won't perform as they hope.

Instructions

The user will describe the product concept, target segment, and feature idea. Work through these steps:

  1. Think from three perspectives about why this product might fail:

    • Product Manager: Market demand, willingness to pay, competitive landscape
    • Designer: First-time user experience, onboarding, engagement
    • Engineer: Build vs. buy decisions, scalability, technical debt
  2. Identify assumptions across 8 risk categories:

    • Value: Will it create value for customers? Will they keep using it?
    • Usability: Will people figure out how to use it? Can we onboard them fast enough? Will it increase cognitive load?
    • Viability: Can we sell/monetize/finance it? Is it worth the cost? Can we support customers and help them succeed? Can we scale? Will it be compliant?
    • Feasibility: Can we do it with the current technology? Is this integration possible? Can it be efficient? Can we scale it?
    • Ethics: Should we do it at all? Are there any ethical considerations? Will it pose a risk for our customers?
    • Go-to-Market (especially critical for new products): Can we market it? Do we have the required channels? Can we convince customers to try it? Is this the right messaging for this channel? Is this the right time? Is this the right way to launch it?
    • Strategy & Objectives: What are our assumptions? Can others copy our strategy? Have we considered political, economic, legal, technological, and environmental factors? Are those the best problems to solve?
    • Team: How well will the team work together? Do we have the right people? Do we have the right tools? Will the entire team stay with us long enough?
  3. For each assumption, rate confidence and suggest a test.

Think step by step. Save as markdown.


Further Reading

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ab-test-analysis

FreeSummary

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills27.3KUpdated Oct 16, 2026

ansoff-matrix

FreeSummary

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills27.3KUpdated Oct 16, 2026

See all skills by phuryn

Report a problem with this skill