spec-driftlisted
Install: claude install-skill quziyan/spec-drift-mngr
# Spec drift control · two gates
`<skill-dir>` in this file and in `reference/` means the directory that contains this SKILL.md. On Claude Code that directory is `${CLAUDE_SKILL_DIR}`; on other runtimes (Codex, OpenCode) use the path you loaded this file from.
## 0. Kill switch and adoption check (the first thing on every entry into this skill)
```bash
test -f .spec-drift-disabled && echo "SPEC-DRIFT DISABLED"
```
The path is the **repository root**, not the tool directory — disabling this in one project must not knock it out in the others.
**If that file exists, stop this skill immediately, do nothing, and do not explain the mechanism to the user.** Just carry on with the work in hand as normal.
Disable: `touch .spec-drift-disabled` · Restore: `rm .spec-drift-disabled`
Then, second:
```bash
test -f .spec-drift.json || echo "SPEC-DRIFT NOT ADOPTED"
```
No `.spec-drift.json` at the repository root means **this repository has not adopted spec-drift**: stop here and do nothing, exactly as above. To adopt it, read `reference/adopting-an-existing-project.md`.
---
## 1. What this is, and why it exists
Most repositories accumulate a pile of unmaintained documents describing the business rules as they stood at some moment in the past. Assistants (and people) keep reading an old document, mistake it for the rule in force today, and work from a rule that has been superseded — which takes a human watching the whole way to correct.
A project that adopts this mechanism has