feedback-triage
starsforks
How to install feedback-triage?
rlaope/oh-my-hermes/feedback-triage
$npx -y skills add rlaope/oh-my-hermes --skill feedback-triage[omh] Hermes Feedback Triage workflow: cluster customer signals and choose the next workflow.
SKILL.md
| 1 | # Feedback Triage |
| 2 | |
| 3 | This is a Hermes-native `feedback-triage` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request already contains an accepted product decision and asks for implementation. |
| 12 | - There are no feedback items, source boundary, or product area to classify. |
| 13 | - The user wants current market research rather than triage of supplied signals. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: Cluster these customer payment failure reports and feature requests before we plan fixes. |
| 20 | - Expected behavior: Cluster bug signals and feature asks, rank severity or opportunity, and recommend research, planning, or coding as a next workflow. |
| 21 | - Why: The input is mixed feedback that needs classification before delivery decisions. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: feedback-triage implement the accepted billing fix now. |
| 26 | - Expected behavior: Route to planning or coding handoff instead of re-triaging. |
| 27 | - Why: The decision is already accepted, so triage would add delay without improving evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The source boundary, signal clusters, severity, and follow-up lane are named. |
| 32 | - Bug, feature, research, strategy, and coding handoff outcomes stay separate. |
| 33 | - The next workflow is recommended before any implementation claim. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If feedback lacks source or severity, ask for the missing signal before coding handoff. |
| 38 | - If the item is actually a plan or research request, route to that workflow instead of triage. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when Hermes should classify feedback, bug reports, and feature asks before deciding whether research, planning, or coding handoff is needed. |
| 55 | |
| 56 | Strong routing signals: `feedback-triage`, `customer-feedback-triage`, `feedback triage`, `customer feedback`, `feedback cluster`, `bug or feature`, `feature request triage`, `payment failure feedback`, `feedback trends`, `payment failure`, `payment failure issue`, `payment failure reports`, `고객 피드백`, `피드백`, `피드백 분류`, `피드백을 모아서`, `결제 실패`, `결제 실패 이슈`, `결제 실패 피드백`, `결제 오류`, `고객 불만`, `버그 제보`, `버그 기능 요청`, `기능 요청` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `triage` |
| 61 | Phase: `feedback` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `triage-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name the source boundary before clustering feedback. |
| 68 | - Classify signals into bug, feature, research, or strategy follow-up without overclaiming evidence. |
| 69 | - Recommend the next workflow instead of jumping straight to coding. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep feedback triage in Hermes; recommend the next workflow and prepare a selected executor/runtime handoff only after explicit coding intent or accepted plan evidence. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - feedback items or summary |
| 78 | - source boundary |
| 79 | - product area |
| 80 | |
| 81 | Expected outputs: |
| 82 | |
| 83 | - clusters |
| 84 | - severity or opportunity ranking |
| 85 | - next workflow recommendation |
| 86 | - product_evidence_loop/v1 |
| 87 | |
| 88 | Artifact expectations: |
| 89 | |
| 90 | - feedback triage record when a wrapper captures it |
| 91 | |
| 92 | Safety rules: |
| 93 | |
| 94 | - Do not turn feedback into a roadmap, implementation plan, or coding handoff by default. |
| 95 | - Separate bug signal, feature ask, severity, opportunity, and missing evidence. |
| 96 | - Route code changes only after explicit user intent or accepted planning evidence. |
| 97 | - product_evidence_lo |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
