averatec-harness-template

Use before any commit, push, or branch/PR decision. Classifies the change as low- or high-risk to pick the right path (direct commit vs branch + PR), and runs a pre-commit checklist so related docs (CHANGELOG / ROADMAP / conventions / memory) move with the code. Does not replace the harness skill — it defers to it for doc sync.

Keep harness docs in sync with shipped code. **MANDATORY before any `git tag -a vX.Y.Z`, `git push origin v*`, or when the user says "ship / release / cut vX.Y.Z"** — verify `CHANGELOG.md` has an entry for that exact version, prune the matching item from `ROADMAP.md`, and review whether `conventions/` needs an update. Also use after committing a new feature, a new structural component, a new pattern reused 3+ times, a breaking change, or whenever the user says "update changelog / roadmap / conventions". Skip for typo fixes and internal refactors with no external impact. Always tell the user one line per file touched.

Create new skills or improve existing ones in this harness. Use when adding a new skill file, rewriting an unclear skill, or improving how a skill triggers.

Use when the user explicitly asks to remember something, sets a rule, or corrects agent behavior. Also use when a meaningful discovery is made that a fresh agent would not derive from the code or git history. Always mention to the user when writing to memory.