Cross-reference spec, CLAUDE.md, code, memory, and knowledge base for inconsistencies. Use periodically or before major implementation steps. Triggers on "health check", "lint knowledge", "check consistency".
You are running a consistency audit across the project's documentation, code, and knowledge base. The goal is to find drift, contradictions, and gaps.
Read these files:
docs/superpowers/specs/2026-04-10-tape-representation-learning-spec.md (spec)CLAUDE.md (conventions and gotchas)knowledge/INDEX.md → then read each linked articleFor each check, record PASS or FAIL with details.
Spec vs CLAUDE.md:
Spec vs Knowledge Base:
Knowledge Base vs Code:
prepare.py and train.py. Does the implementation match the article?Staleness:
last_updated dates more than 7 days old while
their source files have been modified more recently? (Check with git log)Internal Consistency:
For each FAIL:
Also suggest:
Write the report to knowledge/HEALTH_CHECK.md:
# Knowledge Base Health Check
**Date:** <today>
**Status:** X pass / Y fail / Z suggestions
## Failures
### F1: <description>
...
## Suggestions
### S1: <description>
...
Return a 1-2 sentence summary to the caller.