phuryn/pm-skills

identify-assumptions-new

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-new

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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

Think step by step. Save as markdown.


Further Reading

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
phuryn
Communauté

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Installations / 1h
4
GitHub Stars
28,1 k
Mis à jour
8 nov.
phuryn
Communauté

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.
phuryn
Communauté

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.
phuryn
Communauté

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.