// Use when planning recurring multi-agent Hermes workflows after manual delegation works.
Use when creating a fresh Hetzner Cloud VPS with an SSH alias, local project folder, provisioning script, destroy script, and optional handoff into setup-control-room.
Use when bootstrapping an SSH-accessible Ubuntu/Debian VPS with the Agent Control Room template, core agent tooling, and linked control-room skills.
Use when designing, auditing, or documenting backups for Hermes agents without committing secrets.
Use when managing the Agent Control Room: documenting Hermes agents, adding agent folders, updating runbooks, checking architecture, mapping env vars without values, or keeping the control room source of truth consistent.
Use when creating, updating, validating, or explaining the agent registry for a Hermes Agent Control Room.
Use when auditing a VPS-based Hermes agent setup for exposed dashboards, weak secret handling, broad keys, Docker risks, or missing backup/security documentation.
| name | agent-team-cron-planner |
| description | Use when planning recurring multi-agent Hermes workflows after manual delegation works. |
Plan recurring workflows for an established agent team.
Only use after the manual workflow works.
Examples:
Each cron plan should define:
