product-operations-feedback

Builds a closed-loop user feedback system covering collection, classification, validation, and response.

187|12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Luyu2026/Skill-Bible --skill product-operations-feedback-luyu2026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-operations-feedback
Source: https://github.com/Luyu2026/Skill-Bible/tree/main/product-operations/product-operations-feedback
Command: npx skills add https://github.com/Luyu2026/Skill-Bible --skill product-operations-feedback-luyu2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams receive scattered user feedback across app stores, support tickets, communities, and surveys, but often treat every comment as a requirement or let feedback disappear without follow-up. This Skill turns raw feedback into a managed loop: classify it, validate real demand, schedule it into a requirement pool, and respond to users so they know they were heard. ## Core Features & Use Cases - Feedback Classification: Tags incoming feedback as bug, suggestion, complaint, or praise, each routed to its own handling channel (urgent fix, requirement pool, experience optimization, or testimonial material). - Demand Validation Scoring: Scores candidate requirements by frequency, value to core metrics, and feasibility before they enter the requirement pool. - Closed-Loop Response: Produces a response mechanism for handling results, special follow-up for high-frequency reporters, and periodic user feedback processing reports. - Use Case: A product operator aggregates a month of app store reviews and community posts, then uses this Skill to classify them, score the top suggestions, and produce a requirement pool table plus a response plan for users whose ideas were adopted. ## Quick Start Describe your product's current feedback channels and paste recent user feedback, then ask for a complete feedback closed-loop plan covering collection, classification, requirement pool, and response mechanism.

Frequently Asked Questions about product-operations-feedback

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

FAQPage Schema
How do I build a user feedback closed-loop process?▼

A feedback closed loop has five steps: aggregate feedback from multiple channels, classify it by type and priority, validate demand with frequency-value-feasibility scoring, schedule validated items into a requirement pool, and respond to users with handling results. This Skill generates that full plan as a structured document.

How to classify user feedback for a product team?▼

Classify feedback into four types: bugs go to an urgent channel, suggestions become requirement pool candidates, complaints feed experience optimization, and praise becomes testimonial material. Add tags for product module and priority to make triage and reporting consistent.

How do I decide which user suggestions become product requirements?▼

Score each suggestion on three dimensions: frequency (how many users raised it), value (impact on core metrics), and feasibility (cost and technical difficulty). Only items passing this validation enter the requirement pool, which is reviewed and scheduled alongside version planning.

Does this feedback process handle missing product data?▼

Yes. When users do not provide metrics like retention or conversion, the Skill uses industry benchmarks as assumptions and explicitly labels them. Effect attribution is also marked with an evidence level: data, inference, or assumption.

What are the limitations of a feedback-driven requirement pool?▼

Feedback is not the same as demand, so unverified suggestions should not drive the roadmap directly. The Skill provides decision frameworks only; final product decisions remain with the product owner, and incentive programs must account for cost and subsidy phase-out risk.