OMH Triage — Consensus Backlog Grooming

v0.1 status: This skill is deliberately small. It ships with two roles (Maintainer, Skeptic) and is being battle-tested before more roles are added. The full design hypothesis (Maintainer / Operator / Architect / Member-advocate / Skeptic) lives in witt3rd/oh-my-hermes#9. The next concrete milestone (Operator role for version-cut planning pressure) is tracked at witt3rd/oh-my-hermes#11. Roles will be added as lived rounds surface real tensions that the current set cannot represent. The discipline here is learn through use, then expand — the inverse of authoring all five roles up-front against imagined friction.

When to Use

• Periodically grooming an issue backlog (default cadence: before each version cut, when ≥10 issues have accumulated since the last pass, or when a major refactor/migration just landed and may have moved issue premises)
• After a fast-moving development arc (multiple migrations or refactors in days/weeks) that may have superseded several open issues
• When the user says: "triage", "groom the backlog", "walk the issues", "what's stale"

When NOT to Use

• A single ambiguous issue that needs design (use omh-deep-interview then omh-ralplan)
• A backlog that's never been groomed and has hundreds of issues (do a manual first-pass cull first; this skill is for keeping a curated backlog honest, not for archaeology on a rotted one)
• Closing during active dev (don't mix the two-mode discipline — capture during dev, decide during grooming; see the host project's docs/triage/PROCESS.md if it has one)

Prerequisites