| name | launch-feedback-synthesizer |
| slug | aaron-launch-feedback-synthesizer |
| displayName | Launch Feedback Synthesizer · 发布反馈综合 |
| summary | 反馈分诊/状态环/社证收割/you-asked-we-shipped |
| description | Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规 |
| version | 19.2.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when triaging the feedback a launch generates: clustering channel comments, store reviews, feedback-board posts, and support tickets into themes with frequency and severity; running an open→planned→started→completed/declined status loop with subscriber notifications; turning completed requests into you-asked-we-shipped announcement material; or speccing a compliant review/testimonial harvest. The feedback lever of RAMP Proof — not UGC amplification, not outreach execution, not roadmap decisions. |
| argument-hint | <launch slug / feedback exports> [channels] [review platforms] |
| metadata | {"author":"aaron-he-zhu","version":"19.2.0","discipline":"launch","phase":"prove","geo-relevance":"low","hermes":{"tags":["marketing","launch","prove"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Launch Feedback Synthesizer
Triages the feedback a launch generates — channel comments, store reviews, feedback-board posts, support tickets — into themes, runs each theme through a visible status loop, and turns shipped changes and happy users into compliant social proof. This is the feedback lever of the RAMP Prove phase: it feeds the P feedback-loop sub-item (themes, status transitions, requester notification) and the P social-proof-pipeline sub-item (no incentivized store reviews) of the RAMP benchmark. It works one lever and hands off — launch-readiness-auditor rolls the P dimension into the RAMP profile result; this skill never computes it.
Scope guard: this skill triages feedback and specs the proof-harvest protocol only. It does not repurpose or amplify the harvested proof (that is content-amplifier), execute the testimonial outreach threads (that is outreach-manager), make product roadmap decisions (out of scope — it delivers a labeled theme digest to the product owner and stops), record launch stage/date/outcome facts (launch-registry is the sole writer of memory/launch-registry/), or score any RAMP dimension. Always-on comment/DM/mention triage outside the launch window belongs to engagement-inbox-manager — this skill owns launch-window theme triage only. It works one lever — the feedback loop — and hands off.
Quick Start
Triage the feedback from our [product] launch — here are the community comments, the board posts, and the store reviews.
Set up a feedback status loop for [product]: themes, open→planned→started→completed/declined, and notification rules.
Design a review / testimonial harvest for [launch] — which platforms allow incentives, and what exactly do we send?
Skill Contract
Expected output: a feedback theme digest (per theme: frequency, severity, representative quotes), a status-loop spec (transitions, duplicate-merge rule, notification rules), "you asked, we shipped" announcement material for completed themes, a social-proof harvest protocol with a platform compliance matrix, and the standard handoff summary.
