namht-driftlisted
Install: claude install-skill NamHT4Devlop/nam-claude-skill
# namht-drift — does the code still match what the documents say?
Every other skill in this kit works **one change at a time** and leaves evidence. Nobody checks the
**whole picture**: after months of builds, hotfixes and rushed merges, the Knowledge Base slowly
stops describing reality, planned acceptance criteria quietly never ship, and architecture
invariants get broken one exception at a time. This skill is that check.
**Default mode is read-only. It changes nothing** — not the code, not the KB. It produces a report
and hands each finding to the skill that can fix it. Say this to the user up front. The one
exception is the opt-in `--fix-docs` mode below, which still never touches source code.
> **Legacy folder.** Session artifacts used to live in `spec-kit-sessions/` (renamed to avoid
> confusion with GitHub's unrelated `spec-kit` project). If a repo has only the old folder, read
> from it and keep writing to `namht-sessions/`.
## The four kinds of drift (this is the whole job)
| # | Drift | Question it answers | Fix route |
|---|---|---|---|
| D1 | **Stale doc** | The KB describes something the code no longer does | `/namht-rescan` |
| D2 | **Undocumented code** | Real behavior no document mentions | `/namht-rescan` (or `/namht-document`) |
| D3 | **Unbuilt promise** | An AC / planned item from a story or plan that never shipped | `/namht-build` |
| D4 | **Broken invariant** | Code violates the documented architecture rules | `/namht-review` → `/namht-build` |
Anyt