proposal-act

# Proposal Act Take action on a proposal: accept, defer, dismiss, or resolve. ## Step 0 — Channel reply If this skill was invoked from a channel-arrived message (the inbound prompt contains a `<channel source="...">` tag), reply via that channel's reply tool. Otherwise emit to conversation. On a channel-tagged turn, step 4's bounded ask (below) also queues a durable micro-proposal entry via `queue-micro-proposal.ts` — see `channel-responder` § Channel-safe ask bridge — so it survives compaction or a session restart. ## Usage ``` /claude-code-hermit:proposal-act accept PROP-019 /claude-code-hermit:proposal-act defer PROP-015 /claude-code-hermit:proposal-act dismiss PROP-012 /claude-code-hermit:proposal-act resolve PROP-008 /claude-code-hermit:proposal-act accept PROP-019 --answer "session task" ``` The `--answer` form is not typed by an operator — it's how a channel-safe resolution re-enters step 4 after an out-of-band reply (see § Channel re-entry below). If no action or ID is provided, ask the operator which proposal and action. ## Resolving a Proposal ID Before reading any proposal file, resolve the operator's input to a filename: ```bash bun ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-prop.ts .claude-code-hermit "<operator input>" ``` - `MATCH|<filename>` — proceed with that file. - `NONE|not-a-prop-id` — error "Not a PROP id." - `NONE|no-match` — error "No proposal matches [input]. Use /proposal-list to see available proposals." - `AMBIGUOUS|<json array of {file, title...