How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

identify-assumptions-new - Skill

Name: identify-assumptions-new
Author: phuryn

Imported from phuryn/pm-skills (pm-product-discovery/skills/identify-assumptions-new/SKILL.md) via skills.sh. Install upstream with npx skills add phuryn/pm-skills --skill identify-assumptions-new. Copyright stays with the author.

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:

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
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?
For each assumption, rate confidence and suggest a test.

Think step by step. Save as markdown.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "phuryn-pm-skills-identify-assumptions-new", "kind": "skill", "name": "identify-assumptions-new", "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.", "publisher": "phuryn", "version": "1.0.0", "capabilities": { "domains": [ "hr" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/phuryn/pm-skills", "path": "pm-product-discovery/skills/identify-assumptions-new/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/phuryn/pm-skills/identify-assumptions-new", "key": "phuryn/pm-skills/pm-product-discovery/skills/identify-assumptions-new/SKILL.md" } }, "instructions": "## Identify Assumptions (New Product)\n\nComprehensive 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.\n\n### Context\n\nYou are evaluating assumptions for a new product: **$ARGUMENTS**.\n\nIf the user provides files (business plans, research), read them first.\n\n### Domain Context\n\n**The 4 core product risks** (Teresa Torres, *Continuous Discovery Habits*): Value, Usability, Viability, Feasibility.\n\n**For new products, extend t", "cost": { "context_tokens": 735 } }

identify-assumptions-new

About

Identify Assumptions (New Product)

Context

Domain Context

Instructions

Further Reading

Install identify-assumptions-new and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews