Most PMs sit on a chaotic inbound stream — Slack DMs, support tickets, sales call notes, CSAT comments, NPS verbatims, in-app feedback widgets, partner emails, exec one-liners — and have no system for converting that stream into prioritization signal. The default mode is reactive: whoever shouts loudest wins, the loudest channels (sales, executives) dominate, and the actual user job stays invisible.
This skill provides a workflow and a Python tool for handling that stream. Inputs are raw feedback items from many channels. Outputs are deduplicated, categorized, scored, and routed items, plus acknowledgment responses for the customers who sent them.
The frameworks behind it are Marty Cagan's separation of request from opportunity from solution, Noriaki Kano's model of feature-quality categories, a layered customer-development model, and an acknowledge/commit/promise request-management discipline. Detail lives in the references below.
kano_weight × log10(volume+1) × segment_weight × (1 + strategic_alignment) as a coarse router (not a final RICE)discovery/interview-synthesis/).prioritization-frameworks/).Before triaging the feedback, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
segment_weight in the score, i.e. whether enterprise asks outrank long-tail volume).strategic_alignment term that boosts on-strategy asks).Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
The tool does the counting; you do the judgement. It deduplicates by distinct customer, guesses Kano and category from keywords, scores, and routes. It does not name the opportunity or decide what to build.
references/tool-reference.md), one verbatim per ask.python3 project-management/execution/customer-feedback-triage/scripts/feedback_triage.py \
--input project-management/execution/customer-feedback-triage/assets/sample_feedback_queue.json --format markdown
[write the job] keywords: ... until an item carries opportunity_label; replace it with the need ("share results with people who have no login"), not the request ("PDF export").bug-acknowledged reply.decision: will-build | won't-build on the items. Until then every reply is drafted as exploring; suggested_tier is the score's hint, not a commitment. This keeps to "always acknowledge, sometimes commit, rarely promise".Done when every routed cluster has a human-written job label, every reply is exploring or backed by a recorded decision, and no Performance or Basic cluster sits in to_archive (the tool never archives them).
--demo runs a built-in 12-item queue; --format takes json|markdown|mermaid|confluence|notion|linear; --segment-weights 'enterprise=4,smb=1' and --threshold 4.0 tune scoring. Formula, cadence and meeting agenda: references/customer-feedback-triage-guide.md.
Exit codes: 0 report written; 2 missing file, invalid JSON, wrong shape, empty queue or missing required fields.
Mistake: One enterprise account sends 5 messages about CSV export, and its cluster outranks one backed by 14 distinct customers.
Why it happens: Submission count is the number on screen, and repeated messages feel urgent.
Instead: Use distinct customers as volume, so five messages from one account count as 1. Compare distinct_customers to request_count per cluster; a ratio under 0.3 means one shouter.
Mistake: A VP forwards a customer email on Monday and the item tops the roadmap by Tuesday, with no volume check or scoring.
Why it happens: Execs do have customer context, and pushing back on them feels risky.
Instead: Log exec asks with channel exec_ask and run them through the same triage. Send the VP the score and the queue. If more than 30% of roadmap adds over 6 months came from the exec channel, raise it.
Mistake: A customer asks for PDF export and the team builds it. Excel, CSV and Google Sheets requests follow, and each gets built in turn.
Why it happens: The request arrives already shaped as a solution, so it looks ready to build.
Instead: Cluster related requests and write the opportunity_label as a job, such as "share results with people who don't have a login". If the label is a verb plus a file type, rewrite it before scoring.
Nine more, each with a bad and a good example: references/red-flags.md.
| File | Purpose |
|---|---|
scripts/feedback_triage.py | Cluster, score, route, draft replies |
assets/sample_feedback_queue.json | 12-item queue; one cluster carries a human label and one item a will-build decision |
assets/triage_template.md, response_templates.md, kano_quick_reference.md | Manual worksheet, reply templates, Kano card |
examples/triaging-30-requests.md | Worked triage of 30 requests |
feedback_triage.py flags, input schema, and all output schemas. Read when scripting or debugging the tool.In Scope: Inbound feedback intake schema, deduplication and clustering, Kano-based categorization, segment-aware volume scoring, response templating, routing to downstream skills (discovery, prioritization, backlog).
Out of Scope: Bug triage (use the team's bug tracker process). User research and interview-driven discovery (see discovery/interview-synthesis/). Detailed prioritization scoring with RICE/ICE/WSJF (see prioritization-frameworks/). Customer-relationship management (CRM is the system of record for the customer, this skill is the system of record for the request). NPS analysis methodology (this skill ingests NPS verbatims as one channel among many).
Important Caveats: The Kano guess and clustering are transparent keyword/word-overlap heuristics — not ML; override liberally and, above ~500 items/month, augment with semantic clustering offline. The scoring formula is a coarse router, not a substitute for RICE/ICE. "Acknowledge, sometimes commit, rarely promise" is a discipline the templates support but cannot enforce; Sales and CS need explicit training to avoid promising in customer conversations.
| Integration | Direction | What flows |
|---|---|---|
prioritization-frameworks/ | Feeds into | High-priority triaged Feature requests flow in with volume and Kano context as inputs to RICE/ICE/WSJF |
discovery/identify-assumptions/ | Feeds into | Recurring opportunity themes surface implicit product assumptions |
discovery/interview-synthesis/ | Feeds into | Top customers per cluster become the target list for follow-up interviews |
discovery/brainstorm-experiments/ | Feeds into | High-signal opportunities motivate experiment design |
wwas/ | Feeds into | Backlog-ready items move into Why-What-Acceptance format |
job-stories/ | Feeds into | Final backlog items use Job Stories format if team prefers JTBD framing |
senior-pm/ | Bidirectional | Stakeholder map informs segment weights; triage output informs stakeholder updates |
business-growth/customer-success-manager/ | Bidirectional | CS team is the primary intake source via support tickets and CSAT |
sales-success/ | Bidirectional | Sales is the intake source for sales-channel asks; receives won't-build rationale |