Stakeholder Request Intake Organizer

Pro v1.0.0 1 view

Transform scattered feature requests from multiple sources into an organized, prioritized backlog with duplicates identified and urgency signals extracted.

What You Get

Save 4-6 hours of manual organization work by automating categorization, duplicate detection, urgency analysis, and professional backlog description writing. Get from chaos to clarity in 3 minutes.

The Problem

Product managers are overwhelmed by feature requests scattered across Slack threads, email chains, meeting notes, support tickets, and sales CRM. Manually organizing, categorizing, and prioritizing these requests takes 4-6 hours per week. Duplicates slip through, urgency signals are missed (lost deals, churn reasons), stakeholder attribution gets lost, and backlog descriptions are rushed. PMs need a systematic way to process high-volume request intake without losing critical context or spending all day on administrative work.

The Solution

This skill parses unstructured text from any source, extracts distinct feature requests, categorizes them by type (integration, enterprise feature, bug, enhancement, etc.), identifies duplicates across sources, extracts urgency signals (revenue impact, churn, executive directives, support volume patterns), attributes stakeholders clearly, assigns priority levels based on business impact, and generates backlog-ready descriptions with professional formatting. The output is a comprehensive markdown report organized by priority with recommended next steps. The skill transforms 4-6 hours of manual work into a 3-minute automated process while improving quality through systematic urgency detection and duplicate consolidation.

How It Works

  1. 1 Parse raw input text to extract distinct feature requests with stakeholder attribution and dates
  2. 2 Categorize each request by type (integration, enterprise feature, bug, enhancement, performance, pricing, export, technical debt)
  3. 3 Identify and group duplicate requests across different sources and stakeholders
  4. 4 Extract urgency signals including lost deals, churn reasons, executive directives, support volume patterns, and competitive blockers
  5. 5 Assign priority levels (P0/P1/P2/P3) based on business impact, urgency signals, and stakeholder importance
  6. 6 Generate comprehensive intake report with categorized requests, duplicate detection, stakeholder attribution, backlog-ready descriptions, and recommended prioritization for next quarter

What You'll Need

  • Raw request text from any sources (Slack, email, meetings, support tickets, etc.)
  • Optional: Product context for better categorization
  • Optional: Current roadmap focus for alignment
  • Optional: Known priorities (executive directives, strategic initiatives)

Get This Skill

Requires Pro subscription ($9/month)

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements

Examples

CEO Directive with Revenue Impact and Quality Issues

Demonstrates parsing of high-urgency requests from executive leadership (CEO Q2 deadline), sales (lost $40k deal), and support patterns (3 tickets in one week). Shows proper priority assignment (P0/P1), urgency signal extraction, duplicate detection (3 support tickets consolidated), and strategic observations about enterprise readiness themes.

View example

Duplicate Detection Across Multiple Sources

Showcases the skill's ability to identify duplicate requests across different communication channels (Slack, email, support). Salesforce integration requested 2 times (Slack + customer email) gets consolidated into single P1 request. Also demonstrates handling of technical blocker (API rate limits) with appropriate urgency assignment based on customer impact.

View example

Mixed Priority Feature Requests Without Critical Signals

Tests proper handling of lower-priority feature requests without urgent business signals. Demonstrates correct priority assignment based on stakeholder volume (4 customers for Zendesk = P2, 8 users for dark mode = P3, 1 user for CSV = P3). Shows skill appropriately recommends monitoring and deferring lower-priority items while identifying the clearest priority (Zendesk) for next quarter.

View example
View all examples