Feedback Triage

This is a Hermes-native feedback-triage workflow skill.

Why This Exists

feedback-triage exists to keep customer and community signals from jumping straight into roadmap or coding; it clusters evidence, ranks signals, and chooses the next workflow.

Do Not Use When

• The request already contains an accepted product decision and asks for implementation.
• There are no feedback items, source boundary, or product area to classify.
• The user wants current market research rather than triage of supplied signals.
• The triage result asks for a retention or activation intervention rather than another cluster; use omh-lifecycle-growth.
• The supplied material is opportunity records and the request is portfolio health or forecast review; use omh-sales-pipeline-review.
• The request is one reproducible bug with a fix asked for, not a set of reports to cluster; use the coding handoff.

Examples