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 a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly or use strategy-brief for a decision brief instead of starting a leadership operating loop.

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.