Command
/loki-spec-status
Check whether the spec has drifted from its lock using Loki's living-spec drift detection, and summarize the report.
One command from loki-mode.
shell
$ npx -y skills add asklokesh/claudeskill-loki-mode --agent claude-codeShips with loki-mode. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/loki-spec-status
Context preview
What this command does when you run it.
Check whether the spec has drifted from its lock using Loki's living-spec drift detection, and summarize the report.
Stats
Stars1,025
Forks199
LanguageShell
Command definition
loki-spec-status.md
--- description: Check whether the spec has drifted from its lock using Loki's living-spec drift detection, and summarize the report. argument-hint: "[spec-path] (default: prd.md / .loki/generated-prd.md)" allowed-tools: Bash(loki spec:*), Read --- Check whether the spec is still true: the spec is the contract; Loki keeps it true. This runs deterministic drift detection (no LLM cost) comparing the current spec against its lock. Steps: 1. If there is no lock yet, the status command will say so. In that case, offer to create one: ``` loki spec lock $ARGUMENTS ``` The lock (`.loki/spec/spec.lock`) is a deterministic map of spec requirements (checklist items and headings) to content hashes, plus repo HEAD at lock time. 2. Run the drift check: ``` loki spec status $ARGUMENTS ``` Exit 0 means in sync (SPEC-TRUE); exit 1 means drift detected (SPEC-DRIFTED). It writes `.loki/spec/drift-report.json`. 3. Read `.loki/spec/drift-report.json` and summarize for the user: - The verdict: SPEC-TRUE or SPEC-DRIFTED. - Counts of ADDED, REMOVED, and CHANGED requirements, then list each one.