phuryn/pm-skills

identify-assumptions-existing

Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility.

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-existing

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 (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
  1. 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?
  1. 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

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.