[hermes-flavour-mcp-setups] and [hermes-installer-skill] gated only on
[hermes-converter-mvp] (shipped in 6b36b31) — flipped 🔵 → ⚪.
[hermes-mvp-coverage] still blocked on the other two; [hermes-converter-ci]
still blocked on hermes-mvp-coverage.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds the conversion infrastructure for the Hermes-rollout (Nous Research):
- hermes/mapping.yaml — per-skill schema (mode: auto|manual|skip|pending,
category, replace-rules, source override). Every skills/<name>/ has an
explicit entry; the build fails on unmapped skills.
- scripts/build-hermes.py — Python converter. Reads mapping.yaml; for auto
applies replace-rules to SKILL.md and copies the rest verbatim; for manual
copies hermes/skills/<source>/ as-is; for skip / pending records to
dist-hermes/SKIPPED.md.
- dist-hermes/ — pre-converted Hermes-flavour tree (committed; consumed by
the recursive installer in [hermes-installer-skill]). Includes 4 universal
skills: pulling-before-work, active-platform (with Linux+bash replacement
rule), project-discipline, using-markitdown. Plus SKIPPED.md listing
8 skip + 10 pending entries.
- README.md — adds "Build for Hermes" section, updates layout, mentions
hermes/, dist-hermes/, build-hermes.py.
Mapping is the source of truth for the audit table from
.wiki/concepts/hermes-skills-rollout-design.md (Q1-Q8). Pending entries
preserve the audit decision (intended mode/category) for the follow-up
tasks: hermes-flavour-mcp-setups, hermes-installer-skill,
hermes-mvp-coverage. Security carry-forward (extraheader-pattern,
POSIX-absolute paths, semver bumps) — infrastructure ready (replace-rules +
manual mode); concrete content lands in hermes-flavour-mcp-setups.
Smoke-tests: idempotent re-run produces no diff; replace-rules verified on
active-platform (Linux+bash); strict-mapping fail-fast verified on a
synthetic unmapped skill (exit 1).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Shipped in b0d2d51. Coverage check completed inline (acceptance criteria
all have evidence: SKILL.md sections, README mirror, version bump,
build+install verified, smoke-tests covered by self-application).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Part A — Pre-close coverage gate. ### Task completion now lists acceptance
criteria from the per-task file before setting 🟢; missing evidence → ask
the user. New section ### Post-commit task closure prompt: after a feat:/fix:
commit the agent asks "эта работа закрывает таску <slug>?" so shipped code
doesn't sit under stale ⚪ blocks (cf. extend-project-discipline-brainstorm-
workspaces / project-creation-lifecycle-skill, both shipped before close).
Part B — Local-first recommendations at session-start / "what next" triggers.
cwd-project board (🔴 → 🟡 → ⚪) leads; cross-project urgents are at most one
footnote line. Explicit "по всем проектам" flips the order. Pairs with
using-projects-meta's local-first read rule.
Bump 1.0.0 → 1.1.0 (MINOR — adds two new operation types; task block
suggested PATCH but Rule 3 grades these as capability additions). Closes
[using-tasks-close-coverage-gate] (next commit).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Artifacts go to .brainstorm/ or global wiki only via explicit user
direction, never auto-promote by analogy. Fixes gap where brainstorm
outputs in meeting-room/. were incorrectly promoted to .wiki/concepts/
without user command.
Version 0.1.0 → 0.1.1 (MINOR — adds rule).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Three modes now: greenfield-full (new + remote), add-remote, upgrade.
Step 0: detect git/remote/empty state for mode selection.
Step 1.5: Gitea API repo create + push.
Step 8: projects-meta sync for visibility.
Version 1.7.0 → 1.8.0 (MINOR).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Mirror of done [using-projects-meta-fix-paths] for the sister skill.
setup-interns/SKILL.md still uses <project-root>/.common/... (cwd-
relative); should be ~/projects/.common/... like setup-projects-meta.
Surfaced during factory-bootstrap field-test (Phase 1 STOP because
claude inherited cwd C:\Windows\System32, no .common/ child there).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Surfaced during factory-bootstrap field-test on Win11 laptop.
Phase 4 of /setup-projects-meta retries clone with USER:TOKEN@host
URL on auth-failure, which git persists in .git/config of the
cloned repo. Replace with per-invocation extraheader form:
git -c http.extraheader="Authorization: token $T" clone <url>
Field-test artefact: .factory/L0/install-log.md шаг 11c-1.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Native cmdlet equivalent of install.sh: same behavior (copy each
skills/<name>/ into ~\.claude\skills\<name>\, skip if SKILL.md is
missing, support $env:CLAUDE_SKILLS_DIR override and -Names filter).
Removes bash dependency on Windows — no need to invoke git-bash from
pwsh, mirrors the existing build.sh / build.ps1 pair.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Combined the two backlog tasks [active-platform-tuning] +
[active-platform-eval] into a single workstream. Eval IS the tuning
mechanism; "wait for 5 real signals" was a placeholder replaced by
a 20-query synthetic eval set balanced across Win/Lin/Mac.
Spec written at .wiki/concepts/active-platform-eval-design.md
(~150 lines): 20 queries (>=3 should-trigger per OS + near-miss
negatives), run_loop.py 5-iter autoloop in parallel with manual
body sweep (WSL clarity, BSD/macOS expansion, ambiguity policy).
Workspace at .tasks/active-platform-eval/ (eval-set.json committed,
iterations gitignored). Version bump 1.0.0 -> 1.1.0 planned (MINOR).
Pre-flight verified: claude CLI on PATH at C:\nvm4w\nodejs\claude.ps1
(Claude Code 2.1.128); run_loop.py present in skill-creator install.
Both autoloop deps satisfied -- no fallback to manual single-pass.
Per-task file at .tasks/active-platform-eval.md (Goal, Key files,
Decisions log, Open questions, Notes). STATUS.md collapsed the two
original blocks into one paused block; resume point is Q2
(write 20 queries solo vs run skill-creator HTML-review template).
Also fixed in same pause: [install-ps1] STATUS scope expanded to
paired install.sh + install.ps1, cross-platform parity, prune flag
(lesson from [compress-dedup]).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
skills/compress/ was a byte-identical dupe of skills/caveman-compress/
(SHA256 match across all 7 scripts/ files; SKILL.md diff was name: +
Process step 2 only; descriptions textually identical = arbitrary
harness tie-break + double-counted listing budget).
Kept caveman-compress canonical: it carries README.md (benchmarks +
caveman-toolkit branding) and SECURITY.md (Snyk false-positive writeup),
and matches the caveman-* prefix invariant.
Ported the better Process-step wording from compress
(`cd <directory_containing_this_SKILL.md>`) into caveman-compress;
the prior `cd caveman-compress` form assumed cwd was the parent dir
and broke when invoked from ~/.claude/skills/caveman-compress/.
Added version: 1.0.0 to caveman-compress frontmatter
(first versioned release; aligns with skill-versioning concept).
Removed: skills/compress/, dist/compress.skill,
~/.claude/skills/compress/ (manual prune; install.sh has no prune step
yet -- future [install-ps1] task should add --prune).
Slash-command impact: /compress gone; /caveman-compress and
/caveman:compress (toolkit-canonical) remain.
Wiki: .wiki/concepts/compress-dedup.md (rationale + rejected
alternatives), index.md + log.md updated.
Tasks: [compress-dedup] flipped active -> done in same commit
(per-task file .tasks/compress-dedup.md created with full decisions
log).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collapse Step 5.6 from a single-skill detector (only the
superpowers@claude-plugins-official plugin) into a generic
`trigger -> fulfiller` table walker that scales to every canonical
CLAUDE.md trigger.
Inline 9-row map in SKILL.md covers: caveman, superpowers (kind: plugin),
using-wiki, using-tasks, using-projects-meta, pulling-before-work,
project-discipline, using-interns, active-platform. The `kind` flag
(skill | plugin) drives which install command is emitted in the chat-only
recommendation block. Detection paths: ~/.claude/skills/<name>/SKILL.md
for skills, plugins.<id> in ~/.claude/plugins/installed_plugins.json
for plugins.
Algorithm: read project's CLAUDE.md -> match each non-comment line vs
map (substring + tolower, mirrors Step 5 idempotent merge) -> for each
canonical match check disk -> print one chat block listing every missing
fulfiller with copy-pasteable install commands, OR a single
"all dependencies satisfied" line. User-custom lines and removed
canonical lines are silently skipped. Hard rule "never auto-install"
preserved verbatim.
version: 1.6.0 -> 1.7.0 (MINOR per project-discipline Rule 3 -- adds
capability, absorbs prior superpowers-only detector cleanly).
Closes [bootstrap-skill-deps-check] (.tasks/STATUS.md done).
Closes [bootstrap-recommend-projects-meta] by absorption -- the deferred
mirror task was the seed of this generalization; the generic walker now
handles using-projects-meta along with everything else, no per-skill
mirror needed.
Design rationale at .wiki/concepts/bootstrap-skill-deps-check.md:
- why generic over per-skill mirrors (5x mirror explosion)
- skill vs plugin kind distinction
- MCP-server-backed skills (only check using-X policy skill;
setup-X self-fires via Prerequisites pointer)
- source-of-truth invariant: SKILL map + assets/CLAUDE.md.template
must stay in sync (a future CI lint could enforce)
