omh-loop

# Loop This is a Hermes-native `loop` workflow skill. ## Why This Exists `loop` exists for goals whose correct implementation cannot be known upfront but can be discovered through bounded cycles of definition, action, verification, and revision without confusing planned cycles with observed progress. ## Do Not Use When - The user asks for one bounded delivery cycle; use `ultraprocess` or `ultragoal` instead. - The user gives only a north-star outcome such as revenue, stars, or adoption and has not accepted a bounded first loop goal. - The goal is too vague to name an observable problem, next artifact, verification signal, or stop condition. - The goal depends mainly on external waiting, adoption, revenue, or community response without observable local next actions. - The permission profile does not allow repeated research, handoff, queue, or feedback cycles. ## Examples Good example: - Prompt: ./loop make OMH a credible Hermes workflow pack with install, docs, QA, and feedback cycles. - Expected behavior: Start a permission-scoped loop, maintain loop_cycle/v1 state, choose the next concrete task, and keep external outcomes as waiting states. - Why: The request is long-horizon and needs repeated discovery, verification, feedback, and resume decisions. Bad example: - Prompt: ./loop merge this already reviewed one-line README fix. - Expected behavior: Use a direct delivery or PR workflow instead of starting a persistent loop. - Why: The task is bounded and should stop ...