phuryn/pm-skills

outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent.

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 outcome-roadmap

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.

Transform Roadmap to Outcome-Focused Format

Purpose

You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.

Context

Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.

Instructions

  1. Gather Information: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.
  1. Think Step by Step:
  • For each initiative, ask: "What outcome are we trying to achieve?"
  • What customer problem are we solving?
  • What business metric will improve?
  • How will this impact the customer experience or business?
  • Is there a better, different way to achieve the same outcome?
  1. Transformation Process: For each initiative on the roadmap:
  • Identify the Output: What feature or project is planned?
  • Uncover the Outcome: Why are we building it? What changes for customers or business?
  • Rewrite as Outcome Statement: Use this format:
     Enable [customer segment] to [desired customer outcome] so that [business impact]
  1. Example Transformation:
  • Output (Old): Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
  • Outcome (New):
  • Q2: Enable customers to find products 50% faster through intuitive discovery
  • Q2: Increase average order value by 20% through personalized AI recommendations
  • Q2: Help operators monitor all systems with 80% reduction in dashboard load time
  1. Structure Output: Present the transformed roadmap with:
  • Original initiatives listed by quarter/phase
  • Outcome statements for each initiative
  • Key metrics that will indicate success
  • Dependencies or sequencing notes
  1. Include Strategic Context: For the overall roadmap, add:
  • How outcomes align with company strategy
  • Key assumptions about customer needs
  • Flexible release windows (quarters, not specific dates)
  1. Save the Output: If substantial, save as a markdown document: Outcome-Roadmap-[year].md

Notes

  • An outcome should be testable and measurable
  • Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
  • Outcome roadmaps are more resilient to change—embrace flexibility
  • If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value

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.