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: