Cancel

Cancel

This is a Hermes-native cancel workflow skill.

Why This Exists

cancel exists to keep operator work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

• The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
• The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.

Examples

Good example:

• Prompt: cancel: handle a operator request that needs explicit evidence boundaries and a clear stop condition.
• Expected behavior: Run cancel only after naming the target, evidence boundary, and stop condition.
• Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance.

Bad example:

• Prompt: cancel: treat casual chat or unaccepted work as if this workflow already produced verified results.
• Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing cancel.
• Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist

• The local command, managed path, config surface, and state artifact inspected are named.
• Blocking issues, warnings, and optional surfaces are separated.
• The next repair action is explicit and does not claim a reload or runtime observation.

Recovery Notes

• If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
• If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.

Workflow Lane