Automation Blueprint
This is a Hermes-native automation-blueprint workflow skill.
Why This Exists
automation-blueprint exists so Hermes can make recurring operational work feel native and scheduled without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.
Do Not Use When
- An undecided lifecycle journey or growth experiment needs audience, consent, and measurement design before any schedule; use
lifecycle-growth first.
- The user needs a one-off report or deck; use
report-package or materials-package.
- The user asks to review incident metrics once; use
reliability-review.
- The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.
Examples
Good example:
- Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes.
- Expected behavior: Prepare hermes_ops_blueprint/v1 with schedule intent, Slack delivery policy, silence rule, research/report skills, missing evidence, and next confirmation.
- Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed.
Bad example:
- Prompt: automation-blueprint prove the Slack digest was delivered this morning.
- Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened.
- Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery.
Completion Checklist
- Confirm the workflow target, evidence boundary, and stop condition are named.
- Report which outputs are prepared, observed, blocked, or missing.
- Name the smallest next verification or handoff instead of claiming completion from narration.
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.
Workflow Lane
- Current lane: Automation and status (
achievements, workspace-audit, production-audit, automation-blueprint, github-event-ops, github-issue-intake, buzz, agent-board, +35 more) - schedules, status, health, and ops review.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when Hermes should turn a natural recurring/cron-like request into a scheduled ops blueprint without claiming host automation, platform delivery, source retrieval, or no-agent execution.
Strong routing signals: `automation-blueprint`, `scheduled ops`, `scheduled operation`, `scheduled operations`, `automation blueprint`, `cron blueprint`, `cron-ready`, `recurring ops`, `recurring workflow`, `every morning`, `every day`, `daily digest`, `weekly digest`, `automate this`, `automate workflow`, `send to slack`, `send to discord`, `post to telegram`, `only if changed`, `silent if nothing changed`, `schedule this`, `매일`, `매주`, `정기`, `예약`, `반복`, `자동화`, `자동화해줘`, `스케줄`, `슬랙`, `디스코드`, `텔레그램`, `보내`, `공유`, `변화 없으면`, `조용히`
Catalog Metadata
Category: operations
Phase: scheduled-ops-blueprint
Hermes role: operator
Quality tier: ops-blueprint-gated
Reasoning demand: light
Quality bar:
- Name cadence/timezone uncertainty, delivery target, silence/no-change rule, selected skills, and context chain.
- When the recurring work is saved, say it is paused and name what activation needs: explicit overlap, missed-run, retry, backfill, and failure-pause decisions, an approval reference, and an observer from the approved runtime surface.
- Before activation, say what the policy does when a prior run is still active, when a window is missed, and when failures repeat; after a safety pause, report the applied policy and that resuming needs a policy revision.
- Expose whether a no-agent watchdog is a candidate without claiming it exists or ran.
- List host automation, gateway delivery, source retrieval, and no-agent execution as not evidence until observed.
Handoff policy:
Keep schedule intent, delivery policy, silence rules, context-chain selection, and status narration in Hermes; prepare host automation or no-agent follow-up only after an operator/wrapper records observed runtime evidence.
Required inputs:
- recurring request
- schedule or cadence hint
- delivery target or current-thread default
- silence/no-change preference
Expected outputs:
- hermes_ops_blueprint/v1 projection
- hermes_recurring_intent/v1 paused lifecycle record when the user wants the recurring work saved
- schedule/delivery/silence confirmation needs
- status-card boundary
- not-evidence list
Artifact expectations:
- hermes_ops_blueprint/v1 under .omh/hermes-ops/blueprints when a wrapper or CLI records it
- hermes_recurring_intent/v1 under .omh/hermes-ops/recurring-intents when the user asks to save the recurring work
Safety rules:
- Do not claim host cron, Hermes automation, gateway delivery, source retrieval, no-agent execution, plugin load, or connector work from a prepared blueprint.
- Keep scheduled operations as projection metadata until the host runtime supplies observed evidence.
- A saved recurring intent is paused; never report that an occurrence ran without a runtime run reference recorded against that exact intent revision.
- A prepared failure policy is not enforcement: OMH never starts, skips, queues, retries, or backfills an occurrence, and a policy decision is not proof the runtime honoured it.
- Route later coding, material generation, or report delivery into separate accepted handoffs when needed.
Runtime Evidence
Preferred harness for this skill: scheduled-ops-blueprint.
omh runtime record --skill automation-blueprint --harness scheduled-ops-blueprint --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---2name: omh-automation-blueprint3description: [omh] Hermes Scheduled Ops Blueprint workflow: design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status. Use when the user says: automation-blueprint, scheduled ops, scheduled operation, scheduled operations, automation blueprint, cron blueprint, cron-ready, recurring ops.4---5
6# Automation Blueprint
7
8This is a Hermes-native `automation-blueprint` workflow skill.
9
10## Why This Exists
11
12`automation-blueprint` exists so Hermes can make recurring operational work feel native and scheduled without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.
13
14## Do Not Use When
15
16- An undecided lifecycle journey or growth experiment needs audience, consent, and measurement design before any schedule; use `lifecycle-growth` first.
17- The user needs a one-off report or deck; use `report-package` or `materials-package`.
18- The user asks to review incident metrics once; use `reliability-review`.
19- The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.
20
21## Examples
22
23Good example:
24
25- Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes.
26- Expected behavior: Prepare hermes_ops_blueprint/v1 with schedule intent, Slack delivery policy, silence rule, research/report skills, missing evidence, and next confirmation.
27- Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed.
28
29Bad example:
30
31- Prompt: automation-blueprint prove the Slack digest was delivered this morning.
32- Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened.
33- Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery.
34
35## Completion Checklist
36
37- Confirm the workflow target, evidence boundary, and stop condition are named.
38- Report which outputs are prepared, observed, blocked, or missing.
39- Name the smallest next verification or handoff instead of claiming completion from narration.
40
41## Recovery Notes
42
43- If required context is missing, ask one blocking question or route back to the narrower workflow.
44- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
45
46## Workflow Lane
47
48- Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `agent-board`, `+35 more`) - schedules, status, health, and ops review.
49- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
50- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
51
52## Use When
53
54Use when Hermes should turn a natural recurring/cron-like request into a scheduled ops blueprint without claiming host automation, platform delivery, source retrieval, or no-agent execution.
55
56 Strong routing signals: `automation-blueprint`, `scheduled ops`, `scheduled operation`, `scheduled operations`, `automation blueprint`, `cron blueprint`, `cron-ready`, `recurring ops`, `recurring workflow`, `every morning`, `every day`, `daily digest`, `weekly digest`, `automate this`, `automate workflow`, `send to slack`, `send to discord`, `post to telegram`, `only if changed`, `silent if nothing changed`, `schedule this`, `매일`, `매주`, `정기`, `예약`, `반복`, `자동화`, `자동화해줘`, `스케줄`, `슬랙`, `디스코드`, `텔레그램`, `보내`, `공유`, `변화 없으면`, `조용히`
57
58## Catalog Metadata
59
60Category: `operations`
61Phase: `scheduled-ops-blueprint`
62Hermes role: `operator`
63Quality tier: `ops-blueprint-gated`
64Reasoning demand: `light`
65
66Quality bar:
67
68- Name cadence/timezone uncertainty, delivery target, silence/no-change rule, selected skills, and context chain.
69- When the recurring work is saved, say it is paused and name what activation needs: explicit overlap, missed-run, retry, backfill, and failure-pause decisions, an approval reference, and an observer from the approved runtime surface.
70- Before activation, say what the policy does when a prior run is still active, when a window is missed, and when failures repeat; after a safety pause, report the applied policy and that resuming needs a policy revision.
71- Expose whether a no-agent watchdog is a candidate without claiming it exists or ran.
72- List host automation, gateway delivery, source retrieval, and no-agent execution as not evidence until observed.
73
74Handoff policy:
75
76Keep schedule intent, delivery policy, silence rules, context-chain selection, and status narration in Hermes; prepare host automation or no-agent follow-up only after an operator/wrapper records observed runtime evidence.
77
78Required inputs:
79
80- recurring request
81- schedule or cadence hint
82- delivery target or current-thread default
83- silence/no-change preference
84
85Expected outputs:
86
87- hermes_ops_blueprint/v1 projection
88- hermes_recurring_intent/v1 paused lifecycle record when the user wants the recurring work saved
89- schedule/delivery/silence confirmation needs
90- status-card boundary
91- not-evidence list
92
93Artifact expectations:
94
95- hermes_ops_blueprint/v1 under .omh/hermes-ops/blueprints when a wrapper or CLI records it
96- hermes_recurring_intent/v1 under .omh/hermes-ops/recurring-intents when the user asks to save the recurring work
97
98Safety rules:
99
100- Do not claim host cron, Hermes automation, gateway delivery, source retrieval, no-agent execution, plugin load, or connector work from a prepared blueprint.
101- Keep scheduled operations as projection metadata until the host runtime supplies observed evidence.
102- A saved recurring intent is paused; never report that an occurrence ran without a runtime run reference recorded against that exact intent revision.
103- A prepared failure policy is not enforcement: OMH never starts, skips, queues, retries, or backfills an occurrence, and a policy decision is not proof the runtime honoured it.
104- Route later coding, material generation, or report delivery into separate accepted handoffs when needed.
105
106## Runtime Evidence
107
108Preferred harness for this skill: `scheduled-ops-blueprint`.
109
110```sh
111omh runtime record --skill automation-blueprint --harness scheduled-ops-blueprint --status started
112```
113
114Record observed delegation results; otherwise return `not_available` or `not_observed`.
115Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
116- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
117Preserve workflow intent and stop conditions; verify before claiming completion.
118
119Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
120
121Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope