omh-cto-loop

# Cto Loop This is a Hermes-native `cto-loop` workflow skill. ## Why This Exists `cto-loop` exists to keep `leadership` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. ## Do Not Use When - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. ## Examples Good example: - Prompt: cto-loop: run the PM, dev, QA, security, and ops loop for this risky billing launch. - Expected behavior: Prepare the CTO operating model with role responsibilities, gates, blockers, and status boundaries. - Why: The request needs a leadership operating loop, not just a generic plan. Bad example: - Prompt: cto-loop: treat casual chat or unaccepted work as if this workflow already produced verified results. - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `cto-loop`. - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. ## Completion Checklist - Confirm the workflow target, evidence boundary, and stop condition are named. - Report which outputs are prepared, observed, blocked, or missing. - Name the smallest next verification or handoff instead of claiming completion from narration. ## Recovery Notes - If required context is missing, ask one blocking...