🐒 Ming's Note

← Back to Entities

Oh My Hermes

An opinionated workflow layer for Hermes — "like Oh My Zsh is to Zsh." Provides 23 skills, 6 agents, and 5 workflows for autonomous software development operations.

Core Architecture

YOU (founder)
    │  plain-language messages
    ▼
HERMES (24/7)
    │
    ├── CTO Agent (orchestrates, monitors kanban, reports daily)
    │       │
    │       ├── PM Agent (triages issues, prioritizes backlog)
    │       ├── Dev Agent (implements tickets, creates PRs)
    │       ├── Security Agent (scans PRs for secrets, OWASP, CVEs)
    │       ├── QA Agent (reviews PRs, health checks, summaries)
    │       └── Ops Agent (deploys, monitors, handles incidents)
    │
    └── Kanban (Backlog → In Progress → Review → Done)

Key Patterns

1. Kanban as Coordination Layer

Agents don't talk to each other directly. They update kanban cards at each stage. This is the decoupling mechanism — each agent works independently, coordination happens through the shared task board.

2. Agent Specialization

Each agent has: - A defined role (PM, Dev, Security, QA, Ops) - Kanban column ownership - Specific skills they load - Clear boundaries

3. Autonomous + Human Approval

The loop runs automatically (hourly triage, daily reports). Human is only asked for approval at critical decisions:

"Reply YES to ship. Reply NO and tell me why."

4. Skills Organized by Workflow Stage

Not by function, but by when they're used in the lifecycle: 1. Onboarding → Requirements → Brief → Design → Engine selection → Implement → Deploy → Monitor 2. Issue triage → Implement → Review → Approve → Deploy

5. Full Lifecycle Coverage

From idea to running production:

IDEA → clarify-requirements → product-brief → choose-engine → implement → deploy → monitor → triage → repeat

Skills List (23)

Organized by lifecycle stage:

Planning: - onboarding, clarify-requirements, product-brief, design-handoff

Implementation: - choose-engine, implement-with-claude-code, implement-with-codex

Deployment: - deploy-to-vercel, connect-supabase, setup-monitoring, health-check

Operations: - auto-issue-triage, review-github-pr, security-review, await-merge-approval

Support: - send-notification, post-deploy-followup, create-skill, backup-hermes-data

Reusable Patterns for Marketing Operations

Agent Team Structure

Apply same pattern to marketing: - Strategist Agent — audience research, campaign planning - Copywriter Agent — headline, body copy, CTA generation - Designer Agent — visual direction, asset production - Deployer Agent — social media, EDM, print coordination - Analyst Agent — performance tracking, A/B testing, reporting

Kanban for Campaign Flow

Brief → Strategy → Creative → Production → Review → Deploy → Measure

Human Approval Points

Architecture Structure

oh-my-hermes/
├── skills/          ← 23 skill files
├── workflows/       ← 5 workflow files
├── agents/          ← 6 agent role definitions
├── templates/       ← AGENTS.md template, .env example
├── scripts/         ← install, bootstrap, verify, setup-cto
└── docs/            ← Full documentation

Related