synthesize-feedback
Synthesize Feedback
Overview
Perform Voice of Customer (VoC) analysis by clustering raw feedback into themes, quantifying frequency and sentiment, and separating signal from noise. Connects feedback patterns to product roadmap items.
Workflow
-
Read product context — Scan
.chalk/docs/product/for the product profile, existing PRDs, and roadmap docs. These anchor the analysis by providing the product's current priorities and known gaps. -
Gather feedback data — Parse
$ARGUMENTSto identify the feedback source and time period. If the user provides raw feedback inline, use that directly. If they reference files, read them. If no data is provided, ask the user to supply feedback data before proceeding. -
Clean and normalize — For each feedback item, extract the core request or complaint. Strip duplicate phrasing, normalize terminology (e.g., "crash" and "app freezes" map to the same theme), and tag the source channel (support, NPS, review, social, interview).
-
Cluster into themes — Group feedback into 5-10 themes using affinity mapping. Each theme gets a label, a one-sentence description, and representative quotes. Avoid single-item themes unless the signal is strong (e.g., a security concern).
-
Quantify each theme — For each theme, calculate: mention count, percentage of total feedback, average sentiment (positive / neutral / negative), and trend direction (new, growing, stable, declining) if historical data is available.
-
Separate signal from noise — Flag themes that are: (a) high frequency + negative sentiment (urgent), (b) low frequency but high severity (monitor), (c) feature requests from power users vs. casual users (weight accordingly), (d) already addressed in the roadmap (acknowledge).
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
24create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13