topology-driftlisted

Maintainer-only (dwarves-kit repo dev only). Use to audit THIS KIT's OWN feature estate against its path map, "run the topology-drift loop", "is the workflow path map still complete", "does every feature appear in workflow-paths", "feature inventory drift", or after a batch of merges that added/removed commands, agents, skills, or hooks. Cross-checks the generated docs/FEATURES.md registry against the docs/workflow-paths.md path index both directions, then re-places only the DELTA features on the topology diagrams. An audit-loop instance (docs/patterns/audit-loop.md), sibling to /kit:feature-map. REFUSES to run while FEATURES.md is stale (regenerate first). NOT for a consumer/adopter repo (this schema is dwarves-kit-specific; it has nothing to check against there), NOT for auditing a target project you point the kit at (that is /kit:feature-map), NOT for regenerating the registry itself (that is lib/registry/feature-registry.sh, pinned by test-meta), NOT for whole-doc prose drift (that is doc-drift), NOT for
dwarvesf/dwarves-kit · ★ 11 · AI & Automation · score 77

Install: claude install-skill dwarvesf/dwarves-kit

# Topology drift Maintainer-only, dwarves-kit repo development only: this skill audits the KIT'S OWN `docs/FEATURES.md`/`docs/workflow-paths.md` pair, which only exists in this repo. It is not something a consumer/adopter repo would ever have a reason to invoke. To inventory the features of a project the kit is POINTED AT (a migration source, a codebase you want documented), use `/kit:feature-map` instead -- see `docs/patterns/audit-loop.md` for how the two relate. ## Overview Audit the live feature estate (every command, agent, skill, hook) against the workflow path map and ship fixes as a PR. This is the feature-inventory instance of `docs/patterns/audit-loop.md`: the generated registry `docs/FEATURES.md` is the machine truth; `docs/workflow-paths.md` section 5 is the hand-derived path index that drifts when features land or leave. Tier 1 is pure shell; Tier 2 spends model time only on the delta. ## The four slots (per the audit-loop pattern) | Slot | This instance | |---|---| | Item set | every row of `docs/FEATURES.md` plus every line of `docs/workflow-paths.md` section 5 (both sides enumerate; the diff is the queue) | | Contract | (a) FEATURES.md is fresh (regenerating changes nothing); (b) every registry row has exactly one path-index line and vice versa, all four kinds; (c) trigger classes agree between the two (secondary, listed not auto-fixed) | | Evidence class | Tier 1: the repo itself via the generator diff + sed/comm name extraction. Tier 2: a model re-reads