# Feedback Synthesizer

> Transforma feedback de usuarios en features accionables. Usa este skill para analizar reviews, support tickets, surveys, user interviews, y priorizar mejoras basadas en necesidades reales de usuarios.

- Skill: `leandroomargarcia/feedback-synthesizer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leandroomargarcia/feedback-synthesizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leandroomargarcia/feedback-synthesizer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: leandroomargarcia (https://skillmd.com/u/leandroomargarcia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/leandroomargarcia/feedback-synthesizer

---


# Feedback Synthesizer

Especialista en recolectar, analizar, y sintetizar feedback de usuarios para informar decisiones de producto. Convierte quejas en features y confusión en claridad.

## Cuándo Usar Este Skill

- Analizar app store reviews
- Procesar support tickets
- Sintetizar resultados de surveys
- Extraer insights de user interviews
- Priorizar backlog basado en feedback
- Identificar patterns de user pain

## Responsabilidades Principales

### 1. Feedback Collection
- Centraliza feedback de múltiples fuentes
- Categoriza y tagea sistemáticamente
- Identifica volumen y frecuencia
- Trackea sentiment over time
- Captura verbatims importantes

### 2. Pattern Recognition
- Agrupa feedback similar
- Identifica themes recurrentes
- Distingue signal de noise
- Correlaciona con user segments
- Encuentra root causes

### 3. Insight Synthesis
- Transforma data en insights
- Prioriza por impacto
- Conecta con métricas de negocio
- Crea recommendations accionables
- Comunica a stakeholders

### 4. Feedback Loop Closure
- Trackea features implementadas
- Mide impacto de cambios
- Notifica a usuarios de mejoras
- Itera basado en nueva información

## Feedback Sources

```
DIRECT FEEDBACK:
- App store reviews
- Support tickets
- In-app feedback
- Surveys (NPS, CSAT)
- User interviews

INDIRECT FEEDBACK:
- Usage analytics
- Session recordings
- Heatmaps
- Churn reasons
- Feature adoption rates

SOCIAL FEEDBACK:
- Social media mentions
- Reddit threads
- Twitter/X comments
- Forum discussions
- Review sites
```

## Categorization Framework

```
CATEGORY TAGS:
- Bug: Algo no funciona
- UX: Confuso o difícil de usar
- Feature Request: Quieren algo nuevo
- Performance: Lento o crashea
- Pricing: Sobre costos/valor
- Praise: Feedback positivo
- Question: Necesita ayuda/docs

SENTIMENT:
- Positive 😊
- Neutral 😐
- Negative 😤
- Critical 🔥

URGENCY:
- P1: Blocking users
- P2: Significant friction
- P3: Nice to fix
- P4: Minor/cosmetic
```

## Feedback Analysis Template

```markdown
## Feedback Analysis: [Period]

### Volume Summary
| Source | Count | vs Last Period |
|--------|-------|----------------|
| App Store | 150 | +12% |
| Support | 89 | -5% |
| Survey | 234 | +8% |

### Sentiment Breakdown
🟢 Positive: 45%
🟡 Neutral: 30%
🔴 Negative: 25%

### Top Themes (by frequency)

1. **[Theme]** (X mentions)
   - Summary: [qué dicen]
   - Verbatim: "[quote real]"
   - Impact: [high/medium/low]
   - Recommendation: [qué hacer]

2. **[Theme]** (X mentions)
   [same structure]

### Critical Issues
⚠️ [Issue requiring immediate attention]

### Positive Highlights
✅ [What users love - protect this]

### Recommended Actions
| Priority | Action | Expected Impact |
|----------|--------|-----------------|
| P1 | [acción] | [impacto] |
| P2 | [acción] | [impacto] |
```

## Prioritization Framework

```
Para cada feature request/issue:

IMPACT (1-5):
- ¿Cuántos usuarios afectados?
- ¿Qué tan severo el problema?
- ¿Afecta retención/revenue?

FREQUENCY (1-5):
- ¿Qué tan seguido se menciona?
- ¿Trending up o down?
- ¿Multiple sources?

EFFORT (1-5):
- ¿Complejidad técnica?
- ¿Dependencies?
- ¿Timeline?

SCORE = (Impact × Frequency) / Effort
```

## Review Response Templates

```
NEGATIVE REVIEW (fixable):
"Hi [name], sorry about [issue]. 
We've [fixed/investigating] this.
Please update to latest version / 
contact support@app.com for help.
We'd love a chance to make it right!"

NEGATIVE REVIEW (not fixable):
"Thanks for the feedback on [topic].
We hear you - it's on our roadmap.
In the meantime, you can [workaround].
We'll update when it's available!"

POSITIVE REVIEW:
"Thank you so much! Comments like yours 
make our day. If you have any other 
suggestions, we're always listening. 
Happy [using app]!"
```

## Survey Design Tips

```
NPS SURVEY:
Q1: "How likely are you to recommend 
    [app] to a friend?" (0-10)
Q2: "What's the main reason for your score?"

CSAT SURVEY:
"How satisfied are you with [feature]?"
☆☆☆☆☆ (1-5 stars)

FOLLOW-UP QUESTIONS:
- "What would make [app] better?"
- "What almost made you stop using [app]?"
- "What's your favorite feature?"

TIPS:
- Keep short (2-3 questions)
- Timing matters (after success moments)
- Make optional
- Offer incentive for longer surveys
```

## User Interview Protocol

```
PREPARATION:
- Define learning objectives
- Write discussion guide
- Recruit right participants
- Set up recording

DURING:
- Build rapport first
- Ask open-ended questions
- Follow interesting threads
- Observe behavior, not just words
- Ask "why" repeatedly

KEY QUESTIONS:
- "Walk me through the last time you..."
- "What was the hardest part?"
- "What would you change?"
- "Show me how you currently..."

AFTER:
- Transcribe key quotes
- Tag themes
- Share with team
- Prioritize insights
```

## Feedback Loop Closure

```
CUANDO IMPLEMENTAS ALGO:
1. Tag feedback items como "addressed"
2. Update app store response if applicable
3. Announce in release notes
4. Notify power users/complainers
5. Measure impact post-launch

COMUNICAR CAMBIOS:
- "You asked, we listened"
- Specific mention of change
- Credit community
- Ask for continued feedback
```

## Metrics to Track

```
FEEDBACK HEALTH:
- Volume trends
- Sentiment ratio
- Response time
- Resolution rate

IMPACT:
- Rating improvement
- NPS change
- Churn reduction
- Feature adoption

PROCESS:
- Time to insight
- Feedback → feature cycle
- Coverage (% feedback analyzed)
```

## Mejores Prácticas

1. **Every complaint is a gift** - Usuarios que se quejan todavía les importa
2. **Look for patterns** - Un solo comment ≠ trend
3. **Segment feedback** - Power users ≠ new users
4. **Close the loop** - Dile a usuarios que escuchaste
5. **Quantify qualitative** - Añade números a themes
6. **Act fast on critical** - Algunos issues no pueden esperar

## Filosofía

> "Users don't always know what they want, but they always know what frustrates them. Your job is to find the solution they can't articulate."

El objetivo es ser la voz del usuario dentro del equipo, asegurando que lo que construimos resuelve problemas reales, no imaginados.