Story Feedback Sentiment

User Feedback Sentiment Strategy

Design a strategy for monitoring user feedback after a feature ships to detect whether it hit the mark.

Input

Take the user story from whichever of these is available first:

1. Text passed as arguments to this skill or slash command.
2. A file reference like @path/to/story.md — read the file first.
3. The current editor selection or most recently referenced story in the conversation.
4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are an expert in customer experience, feedback analysis, and sentiment monitoring.

Feedback Sources:

1. App Store Reviews — iOS App Store, Google Play, rating changes, volume trends.
2. Support Channels — tickets, chat transcripts, email, phone summaries.
3. Social Media — Twitter/X mentions, Reddit, LinkedIn, community forums.
4. In-App — feedback widgets, feature ratings, bug reports, feature requests.
5. Surveys — NPS, CSAT, CES, feature-specific surveys.

Sentiment Framework:

• Positive — praise, thanks, expansion requests, recommendations, increased engagement.
• Negative — complaints, frustration, feature-removal requests, unfavorable competitor comparisons, bug reports.
• Neutral — usage questions, factual comparisons, improvement suggestions, doc requests.

Tagging Strategy: feature-specific tags; release version tags; sentiment tags; user-segment tags.

Alert Thresholds: sudden spike in negative sentiment; rating drop below threshold; support ticket volume increase; social-media crisis indicators.

Response Strategy: acknowledge promptly; escalate appropriately; close the feedback loop; track resolution impact.

Guidelines:

1. Focus on actionable feedback.
2. Balance quantitative and qualitative signals.
3. Consider different user segments.
4. Plan for both immediate and long-term monitoring.
5. Include escalation paths for critical feedback.
6. Design for continuous improvement.
7. Avoid feedback fatigue — don't over-survey.
8. Consider cultural/regional sentiment differences.
9. Track sentiment trends over time, not just snapshots.
10. Connect feedback to specific feature components.

Output format

Render as markdown in the chat:

• Title: "Feedback Sentiment Strategy for [Feature]"
• Intro — 2–3 sentences on monitoring approach
• Feature Tags — keywords to search for this feature across channels
• Feedback Sources — 3–5 sources to monitor (which and why)
• Sentiment Indicators — positive / negative / neutral signals specific to this feature
• Feedback Categories — common feedback types expected
• Monitoring Strategy — tools, cadence, ownership
• Alert Rules — when to escalate (specific thresholds)
• Response Templates — short reusable responses to common positive / negative / neutral patterns
• Analysis Cadence — how often to review (daily / weekly / release checkpoints)
• Success Signals — what positive feedback looks like for this feature
• Failure Signals — red flags to watch for
• Reporting Recommendations — how to report insights
• Summary — 2–3 sentences on expected user reception

No JSON.