meta(tasks): create [tdd-criteria-hermes-mapping] in claude-skills

.tasks/STATUS.md

@@ -322,3 +322,28 @@ version: 0.1.0
 <!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: .meeting-room / 2026-05-07T04:02:05.413Z -->
 
 ---
+
+## 🔵 [tdd-criteria-hermes-mapping] — Add entry for `tdd-criteria` skill to `~/projects/claude-skills/hermes/mapping.yaml`. Required step — `build-hermes.py` fails on unmapped skills.
+
+**Entry (place alphabetically among `auto`-mode skills, after `project-discipline`):**
+
+```yaml
+  tdd-criteria:
+    mode: auto
+    category: software-development
+```
+
+**No `replace-rules`** — the skill is pure policy (no Claude-tool refs like `Read`/`Edit`/`Bash`/`Glob` in SKILL.md body). Verified by `tdd-criteria-skill-write` task constraints.
+
+**Verification step:** run `python ~/projects/claude-skills/scripts/build-hermes.py` after edit — output must include `tdd-criteria` in the converted list under `dist-hermes/software-development/tdd-criteria/`. If build fails on `Unmapped skill: tdd-criteria` the entry didn't take; if it fails with replace-rule errors, the SKILL.md inadvertently has Claude-tool refs (loop back to `tdd-criteria-skill-write` to clean).
+
+**Out of scope:** no Hermes-side install / activation (Hermes side handled by `hermes-mvp-coverage` task family separately). This task only ensures the converter knows about the skill.
+
+**Status:** blocked
+**Where I stopped:** (not started)
+**Next action:** Дождаться 🟢 у `tdd-criteria-skill-write`. Edit `hermes/mapping.yaml`: вставить entry в alphabetical порядке среди `auto`-mode-секции (после `project-discipline:`). Прогнать `python scripts/build-hermes.py` — убедиться что `dist-hermes/software-development/tdd-criteria/SKILL.md` создаётся без ошибок. Закоммитить mapping.yaml + dist-hermes/.../tdd-criteria/ одним коммитом.
+**Blocker:** tdd-criteria-skill-write
+**Branch:** master
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: .meeting-room / 2026-05-07T04:02:21.684Z -->
+
+---