Claude Code occasionally fails to follow project memory instructions (CLAUDE.md)

Bug Description

Claude Code occasionally stops following the project-specific instructions defined in CLAUDE.md, even though these instructions are loaded and visible in context. This has happened multiple times across different sessions.

Expected Behavior

Claude Code should consistently follow all instructions in CLAUDE.md throughout the entire session, including:

• Version bumps after completing features/fixes
• Updating documentation (SCHEMA-REFERENCE.md, IMPLEMENTATION-LOG.md, version.html)
• Running pre-deployment checklists
• Auditing PostHog analytics tracking

Actual Behavior

Claude Code follows the instructions initially but then "forgets" to follow them partway through a session. The user has to explicitly remind Claude to check its memory instructions.

Examples of forgotten tasks:

• Not bumping version numbers after completing bug fixes
• Not updating IMPLEMENTATION-LOG.md after implementing features
• Not adding changelog entries to version.html
• Not auditing PostHog tracking after adding new features

Steps to Reproduce

1. Create a CLAUDE.md with specific post-feature instructions (e.g., "After completing a feature, update version in X, Y, Z files")
2. Have Claude implement a multi-step feature
3. Observe that Claude completes the feature but skips the post-feature documentation tasks
4. User must explicitly ask "why did you stop following your memory instructions?" to trigger compliance

Environment

• Claude Code CLI
• Model: Claude Opus 4.5
• Project with CLAUDE.md memory file containing 15+ critical rules

Impact

• Incomplete documentation
• Version drift between files
• Missing analytics tracking for new features
• User must manually audit and remind Claude, defeating the purpose of memory instructions

Suggested Improvement

Consider adding a checkpoint mechanism that reviews CLAUDE.md instructions after completing major tasks, similar to how todo lists are used to track work progress.