phuryn/pm-skills

analyze-feature-requests

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/phuryn/pm-skills --skill analyze-feature-requests

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Analyze Feature Requests

Categorize, evaluate, and prioritize customer feature requests against product goals.

Context

You are analyzing feature requests for $ARGUMENTS.

If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.

Domain Context

Never allow customers to design solutions. Prioritize opportunities (problems), not features. Use Opportunity Score (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the prioritization-frameworks skill for full details and templates.

Instructions

The user will describe their product goal and provide feature requests. Work through these steps:

  1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
  1. Categorize requests into themes: Group related requests together and name each theme.
  1. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
  1. Prioritize the top 3 features based on:
  • Impact: Customer value and number of users affected
  • Effort: Development and design resources required
  • Risk: Technical and market uncertainty
  • Strategic alignment: Fit with product vision and goals
  1. For each top feature, provide:
  • Rationale (customer needs, strategic alignment)
  • Alternative solutions worth considering
  • High-risk assumptions
  • How to test those assumptions with minimal effort

Think step by step. Save as markdown or create a structured output document.


Further Reading

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
phuryn
Comunidad

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.

Instalaciones / 1h
4
GitHub Stars
28,1 mil
Actualizado
8 nov
phuryn
Comunidad

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.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov
phuryn
Comunidad

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.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov
phuryn
Comunidad

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.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov