prd-v09-feedback-loop-setup_skill

Overview

This skill sets up repeatable channels and processes to capture, process, and act on post-launch feedback during PRD v0.9 Go-to-Market. It converts raw user input into structured CFD- entries and links feedback into the ID graph so product teams can prioritize and close the loop. The goal is measurable feedback flow, not just data collection.

How this skill works

On trigger, the skill maps touchpoints and configures capture points (in-app widgets, support taxonomy, surveys, community hooks, analytics). Incoming items are routed to a central inbox, triaged by priority and SLA, and turned into CFD- entries using a standard template. CFD- entries are linked to BR-, FEA-, RISK-, or EPIC- IDs and tracked through response and resolution workflows.

When to use it

• When launching v0.9 or any post-launch release
• When asked “how do we collect feedback?” or “feedback loop”
• To set up NPS, CSAT, CES, or feature request capture
• When support volume, sentiment, or performance issues spike
• To convert community threads or survey responses into product work items

Best practices

• Prioritize capture channels: in-app for context, support for issues, community for ideas, analytics for passive signals
• Daily/weekly triage with SLAs: Critical <4h, High <24h, Medium/Low weekly
• Always create a CFD- entry for actionable feedback and link to BR-/FEA-/RISK- IDs
• Track volume, sentiment, response time, and resolution rate to baseline and measure improvement
• Close the loop with users for High+ priority items and publicly acknowledge community requests

Example use cases

• Add an in-app NPS widget to measure promoter/detractor trends monthly and generate CFD- NPS entries
• Convert repeated support tickets about exports into CFD- entries, create FEA- backlog items, and escalate revenue risk
• Monitor rage clicks and drop-offs; capture passive signals and create CFD- entries for UX investigation
• Triage Discord feature threads into CFD- entries, estimate affected users, and add to EPIC planning
• Run post-release feature satisfaction surveys and feed results into prioritization meetings