Use immediately after running telesis init on an existing project, or when the user asks to validate generated documentation. Provides a systematic checklist for verifying ARCHITECTURE.md, PRD.md, MILESTONES.md, and VISION.md against the actual codebase, plus guidance for recovering content from a pre-existing CLAUDE.md.
Use this after telesis init on an existing codebase. The generated docs may contain hallucinated structure or incorrect assumptions.
ls/find output — no fabricated directoriesAs of v0.27.3, telesis init automatically preserves existing CLAUDE.md sections as notes:
telesis note list -t preserved-claude-md # Check preserved content
If that didn't capture everything, recover manually:
git show HEAD~1:CLAUDE.md # View the old content
git diff HEAD~1:CLAUDE.md CLAUDE.md # See what changed
Create notes for operational content not captured in generated docs:
telesis note add -t rules "Always use snake_case for database columns"
telesis context # Regenerate CLAUDE.md with notes
internal/ packages that don't exist# 1. Fix docs to match reality
# 2. Create notes for operational content
telesis note add -t rules "..."
# 3. Regenerate context
telesis context
# 4. Verify drift
telesis drift