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