Claude Worker Patch Loop

Use this when you want Claude to act as a specialist worker that directly edits files, while the main session stays as orchestrator/reviewer.

Best for:

• refining skills, workflows, policies, and route definitions
• applying a batch of structured documentation/process edits
• tightening a canonical file over several review/patch cycles
• using Claude for execution while Hermes keeps orchestration, verification, and synthesis

When to use

Choose this pattern when:

• the work is non-trivial but file-local or small-batch
• you want Claude to make edits directly, not just give advice
• you already know the target file(s)
• you want an external worker to improve wording/structure while preserving orchestration discipline