# Omh Decision Recall

[omh] Previously rejected options to revisit: recall scoped reviewed rejected decisions...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-decision-recall -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-decision-recall -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-decision-recall -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-decision-recall -g -a gemini-cli -y`

## Description

[omh] Previously rejected options to revisit: recall scoped reviewed rejected decisions without elevating them to approved memory. Use when the user says: decision-recall, rejected decision recall, rejected decisions, why was this rejected, previously rejected alternative, 거절된 결정, 기각된 대안.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Decision Recall

This is an OMH `decision-recall` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`decision-recall` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.

## Do Not Use When

- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.

## Examples

Good example:

- Prompt: Show rejected decisions for this project before we choose an alternative.
- Expected behavior: Produce `show_rejected_decision_recall` with required context, wrapper actions, and not-evidence boundaries.
- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.

Bad example:

- Prompt: Claim the recalled rejected decision is an approved memory write or proof the replacement ran.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

## Completion Checklist

- The query, scope, tags, stale policy, and match limit are explicit.
- Only reviewed rejected candidates are returned; expired candidates stay excluded.
- Recall output is not presented as approved memory, source freshness, or execution evidence.

## Recovery Notes

- If required context is missing, ask one blocking question or route back to the narrower workflow.
- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.



## When to Use

Use for scoped reviewed rejected-decision context; it is not approved memory or execution evidence.

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-decision-recall/SKILL.md