analyze-feature-requests

Analyze feature requests into problem themes, priorities, risks, and requirement candidates.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill analyze-feature-requests-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-feature-requests
Source: https://github.com/jason23452/my-skill/tree/main/flow/analyze-feature-requests
Command: npx skills add https://github.com/jason23452/my-skill --skill analyze-feature-requests-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often receive a messy mix of feature requests, customer asks, and stakeholder demands as backlogs, spreadsheets, notes, or ADO items. This Skill turns that raw request list into structured opportunity themes, priorities, and requirement candidates instead of letting requesters dictate solutions. ## Core Features & Use Cases - Request Normalization: Extracts requester, user, situation, requested solution, underlying need, evidence, and urgency from each item. - Theme Grouping & Scoring: Groups requests by user problem or job-to-be-done and scores each theme on impact, effort, risk, and strategic alignment. - SDD Output: Produces opportunityThemes, prioritizedRequirementCandidates, deferredOrRejectedRequests, assumptions, and openQuestions for a Requirements Agent. - Use Case: Given a spreadsheet of 40 customer asks, use this Skill to cluster them into problem themes, identify the top opportunities with rationale and validation needs, and explicitly name deferred non-goals for requirements.md. ## Quick Start Analyze this backlog of feature requests and stakeholder asks into prioritized opportunity themes and requirement candidates for our requirements document.

Frequently Asked Questions about analyze-feature-requests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a backlog of feature requests?▼

Normalize each request by extracting requester, user, situation, requested solution, underlying need, evidence, and urgency. Then group items by user problem or job-to-be-done and score each theme on impact, effort, risk, and strategic alignment.

How to prioritize feature requests from customers and stakeholders?▼

Group requests into problem themes rather than UI components, then qualitatively score each theme on user value, delivery complexity, market or technical risk, and alignment with product goals. Produce top opportunities with rationale and minimal validation needed.

What inputs does feature request analysis support?▼

It accepts backlogs, spreadsheets, notes, ADO items, or any mixed request list. It is designed for cases where input is many raw asks rather than one clearly defined requirement.

What output does this analysis produce for requirements documentation?▼

It produces opportunityThemes, prioritizedRequirementCandidates, deferredOrRejectedRequests, assumptions, and openQuestions. The resulting requirements.md describes selected product opportunities and explicitly names non-goals rather than listing raw requests.

When should I not use feature request analysis?▼

Avoid it when you already have one clear, well-defined requirement, since the grouping and scoring process adds no value. It is meant for ambiguous, high-volume request inputs during product discovery, not single-requirement refinement.