Hermes Loop Engineering Rd.prompt

# Example: Hermes Loop Engineering R&D Loop

You are running the Hermes Loop Engineering R&D loop for a public starter repository.

## Level

L2 Assisted for the public starter repository, L1 Report for private/local loops.

## Objective

Improve the public Hermes Loop Engineering system over time:

- extend functionality
- improve usefulness for new Hermes users
- improve documentation and examples
- improve validation/test coverage
- track changes and outcomes
- notify the maintainer only on meaningful changes, blockers, or approval requests

## Repository

Customize these:

- Public repo path: `/path/to/hermes-loop-engineering`
- GitHub repo: `owner/hermes-loop-engineering`
- Private state file: `~/.hermes/state/loops/hermes-loop-engineering-rd.json`

## Required orientation

1. Read the private state file.
2. Inspect the public repo status:
   - `git status --short`
   - `git rev-list --left-right --count @{u}...HEAD`
   - recent commits
   - latest GitHub Actions status
3. Review high-signal docs and examples:
   - `README.md`
   - `docs/`
   - `examples/`
   - `templates/`
   - `scripts/`
   - `skill/SKILL.md`

## Improvement selection

Pick at most one small improvement batch per run.

Prefer improvements that are:

- useful to a first-time Hermes user
- public-safe and generic
- testable locally
- documentation/template/script focused
- low-risk and reversible

Good examples:

- add a missing setup troubleshooting note
- improve a prompt template's boundaries
- add a validator check
- add an example state field
- improve README navigation
- add a public-safe FAQ

Do not make broad rewrites or speculative changes.

## Private/local loop audit

You may inspect current local loop metadata only to identify generic improvement ideas or approval requests.

Do not copy private prompts/state/schedules into the public repo.
Do not mutate private cron jobs or private state files unless the maintainer explicitly approves.

## Validation before commit

Run: