feedback_skill

Overview

This skill helps founders turn chaotic user feedback into clear product decisions. It covers feedback collection methods, survey design (including NPS), feature request management, prioritization frameworks, and practices for closing the feedback loop. Use it to build a repeatable feedback-driven product process that reduces churn and guides the roadmap.

How this skill works

The skill outlines where to collect high-signal feedback (1:1 calls, support tickets, in-app widgets, cancellation surveys, analytics) and when to use each method as you grow. It provides templates and requirements for implementing an in-app feedback widget and running quarterly NPS surveys, plus a pragmatic prioritization formula (Impact × Confidence / Effort). Finally, it includes workflows for a request board, processing incoming requests, and notifying users when items ship.

When to use it

• You need to collect contextual, in-product feedback without third-party tooling.
• You want to implement NPS and follow-up flows to track sentiment over time.
• You must aggregate and prioritize feature requests from many channels.
• You need a repeatable process to turn feedback into roadmap decisions.
• You want to improve retention by closing the feedback loop with users.

Best practices

• Start simple: centralize all feedback into one system you actually use.
• Talk to every user early; add widgets and surveys as you scale.
• Always ask 'why' — translate requests into underlying problems.
• Prioritize by measurable impact, confidence, and effort (hours).
• Close the loop: notify users when you ship features they requested.

Example use cases

• Add a bottom-right feedback button that captures page URL, user ID, and a free-text comment to a feedback table.
• Run a quarterly NPS for users active 30+ days with an open-text follow-up and targeted follow-ups by score band.
• Set up a public or internal feature request board with upvotes, tags, and status columns (Under Review, Planned, In Progress, Shipped, Won't Do).
• Analyze support tickets weekly to uncover recurring pain points and prioritize quick fixes that reduce churn.
• Send monthly changelogs highlighting features shipped from user feedback and upcoming plans.