mcpField
F
feature-request-prioritization-review

feature-request-prioritization-review

github.com/sylphxaiProductivity135 installsUpdated today
Repository

About feature-request-prioritization-review

A skill for evaluating and prioritizing feature requests using evidence, user segments, impact, and delivery constraints. It distinguishes request types and supports a reasoned decision and customer follow-up.

Key features

  1. 01Request type classification
  2. 02Evidence scoring and duplicate clustering
  3. 03Segment and strategic fit review
  4. 04Impact, effort, and risk assessment
  5. 05Decision and customer response planning

Use cases

  1. 01Compare requests from different user segments
  2. 02Separate bugs from workflow blockers
  3. 03Explain a prioritization decision to stakeholders

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill feature-request-prioritization-review

After installing, type/feature-request-prioritization-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/feature-request-prioritization-patterns.md

Details

From the project README

Feature Request Prioritization Review

Use this skill to convert feature request prioritization, evidence quality, duplicate clustering, segment fit, roadmap, and close-the-loop questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify request source, affected users, segment, job/pain, evidence, frequency, revenue/retention impact, strategic fit, current workaround, and delivery constraints.
  2. Read references/feature-request-prioritization-patterns.md.
  3. Classify request as bug, usability gap, workflow blocker, enterprise ask, compliance/security need, pricing/package gap, integration, power-user enhancement, or strategic bet.
  4. Define evidence score, clustering, opportunity framing, impact/effort/risk, dependency map, decision owner, communication plan, and revisit trigger.
  5. Produce prioritization review, state machine, decision table, event schema, scoring checklist, and stakeholder response.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not rank by loudest customer, biggest logo, newest ticket, or sales urgency alone.
  • Do not promise roadmap dates until ownership, scope, tradeoffs, and delivery confidence are approved.
  • Do not merge bugs, support confusion, workflow jobs, and strategic bets into one undifferentiated request list.
  • Do not close the loop with vague “maybe later” when the decision and reasoning are known.

Output format

Request context:
Audience / source of truth / risk boundary:

Prioritization plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Evidence, tradeoffs, decision, and customer response:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported