omh-feedback-triage

# 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. ## Examples Good example: - Prompt: Cluster these customer payment failure reports and feature requests before we plan fixes. - Expected behavior: Cluster bug signals and feature asks, rank severity or opportunity, and recommend research, planning, or coding as a next workflow. - Why: The input is mixed feedback that needs classification before delivery decisions. Bad example: - Prompt: feedback-triage implement the accepted billing fix now. - Expected behavior: Route to planning or coding handoff instead of re-triaging. - Why: The decision is already accepted, so triage would add delay without improving evidence. ## Completion Checklist - The source boundary, signal clusters, severity, and follow-up lane are named. - Bug, feature, research, strategy, and coding handoff outcomes stay separate. - The next workflow is recommended before any implementation claim. ## Recovery Notes - If feedback lacks source or severity, ask for the miss...