cto-loop
starsforks
How to install cto-loop?
rlaope/oh-my-hermes/cto-loop
$npx -y skills add rlaope/oh-my-hermes --skill cto-loop[omh] Hermes CTO Loop workflow: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence.
SKILL.md
| 1 | # Cto Loop |
| 2 | |
| 3 | This is a Hermes-native `cto-loop` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `cto-loop` exists to keep `leadership` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. |
| 12 | - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. |
| 13 | |
| 14 | ## Examples |
| 15 | |
| 16 | Good example: |
| 17 | |
| 18 | - Prompt: cto-loop: run the PM, dev, QA, security, and ops loop for this risky billing launch. |
| 19 | - Expected behavior: Prepare the CTO operating model with role responsibilities, gates, blockers, and status boundaries. |
| 20 | - Why: The request needs a leadership operating loop, not just a generic plan. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: cto-loop: treat casual chat or unaccepted work as if this workflow already produced verified results. |
| 25 | - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `cto-loop`. |
| 26 | - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. |
| 27 | |
| 28 | ## Completion Checklist |
| 29 | |
| 30 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 31 | - Report which outputs are prepared, observed, blocked, or missing. |
| 32 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 33 | |
| 34 | ## Recovery Notes |
| 35 | |
| 36 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 37 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 38 | |
| 39 | ## OMH Context Rail |
| 40 | |
| 41 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 42 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 43 | - Current lane: **Coding handoff** (`idea-to-deploy`, `cto-loop`, `deploy-and-monitor`, `code-review`, `build-failure-triage`, `verification-gate`, `security-safety-review`, `ultrawork`, `+7 more`) - coding owners, handoffs, review, CI, and merge evidence. |
| 44 | - 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. |
| 45 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 46 | - 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. |
| 47 | - Coverage: Every generated workflow skill carries this rail. |
| 48 | - Normal users talk to Hermes; OMH CLI is infra. |
| 49 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 50 | |
| 51 | ## Use When |
| 52 | |
| 53 | Use when Hermes should run a leadership-style operating loop that turns signals into roadmap decisions, technical tradeoffs, delivery risk, release readiness, and explicit follow-up handoffs. |
| 54 | |
| 55 | Strong routing signals: `cto-loop`, `cto loop`, `cto`, `cto pm`, `pm dev qa security ops`, `roadmap technical tradeoffs`, `technical tradeoff`, `delivery risk`, `release readiness`, `technical leadership loop`, `leadership operating loop`, `engineering leadership`, `CTO 구조`, `PM 구조`, `로드맵`, `아키텍처 트레이드오프`, `기술 리더십`, `출시 준비` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `leadership` |
| 60 | Phase: `operating-loop` |
| 61 | Hermes role: `operator` |
| 62 | Quality tier: `decision-gated` |
| 63 | |
| 64 | Quality bar: |
| 65 | |
| 66 | - Separate product priority, architecture tradeoff, delivery risk, release risk, and follow-up owner. |
| 67 | - Tie recommendations to observed signals or mark assumptions. |
| 68 | - Record accepted decisions separately from draft recommendations. |
| 69 | - Prepare executor handoffs only for accepted implementation follow-ups. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep CTO/PM-style synthesis, tradeoffs, risk ranking, decision notes, and status in Hermes; convert accepted implementation follow-ups into executor-neutral handoffs. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - operating signals |
| 78 | - roadmap or release scope |
| 79 | - known risks |
| 80 | - decision owner |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - priority frame |
| 85 | - architecture tradeoffs |
| 86 | - delivery risks |
| 87 | - decision note |
| 88 | - follow-up handoff candidates |
| 89 | |
| 90 | Artifact expectations: |
| 91 | |
| 92 | - leadership loop record or status summary when a wrapper captures decisions and follow-ups |
| 93 | |
| 94 | Safety rules: |
| 95 | |
| 96 | - Do not treat a CTO loop recommendation as an accepted roadmap decision. |
| 97 | - Do not impl |
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
