operating-rhythm
starsforks
How to install operating-rhythm?
rlaope/oh-my-hermes/operating-rhythm
$npx -y skills add rlaope/oh-my-hermes --skill operating-rhythm[omh] Hermes Operating Rhythm workflow: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history.
SKILL.md
| 1 | # Operating Rhythm |
| 2 | |
| 3 | This is a Hermes-native `operating-rhythm` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `operating-rhythm` exists so recurring operating work has durable minutes, decisions, and follow-up history without pretending a meeting outcome was observed. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user only needs a one-off meeting agenda before the meeting; use `meeting-brief`. |
| 12 | - The request is a weekly status/risk summary rather than cadence history; use `ops-review`. |
| 13 | - The user asks for report packaging, PPT outline, or reliability evidence review. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: operating-rhythm 회의록 히스토리 관리하고 스크럼 스프린트 회고를 정리해줘. |
| 20 | - Expected behavior: Create a prepared operating record with cadence, decisions, action items, and not-evidence markers for missing observed notes. |
| 21 | - Why: The request is about recurring operating history, not a generic agenda or code handoff. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: operating-rhythm implement the action items from the retro. |
| 26 | - Expected behavior: Route implementation to a plan or selected executor/runtime handoff after action items are accepted. |
| 27 | - Why: Operating records can capture follow-ups, but implementation is a separate observed work stream. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 32 | - Report which outputs are prepared, observed, blocked, or missing. |
| 33 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 38 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when Hermes should prepare or maintain recurring operating records such as meetings, scrums, sprint plans, retrospectives, decisions, and follow-ups. |
| 55 | |
| 56 | Strong routing signals: `operating-rhythm`, `operating rhythm`, `meeting minutes`, `meeting history`, `scrum record`, `sprint planning`, `sprint review`, `sprint retrospective`, `retro history`, `decision log`, `action item history`, `회의록 관리`, `회의 히스토리`, `운영 리듬`, `스크럼`, `스프린트 회고`, `결정 기록`, `액션 아이템` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `operations` |
| 61 | Phase: `rhythm-history` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `operations-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name cadence, audience, time window, known notes, and missing evidence before producing a record. |
| 68 | - Separate agenda/templates from observed minutes, decisions, and action items. |
| 69 | - Record follow-up ownership only when supplied or explicitly mark it unknown. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep cadence records, minutes scaffolds, decisions, and follow-up history in Hermes; delegate implementation only from separately accepted action items. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - cadence or meeting type |
| 78 | - audience or participants |
| 79 | - time window |
| 80 | - source notes or explicit missing-notes boundary |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - operation artifact |
| 85 | - decision log |
| 86 | - action item history |
| 87 | - observed/prepared boundary |
| 88 | |
| 89 | Artifact expectations: |
| 90 | |
| 91 | - operation_artifact/v1 under .omh/operations when a wrapper or CLI records it |
| 92 | |
| 93 | Safety rules: |
| 94 | |
| 95 | - Do not treat a prepared record as proof that the meeting or scrum happened. |
| 96 | - Do not mark decisions or action items accepted without supplied notes or owner acknowled |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
