Your AI Is Working Off Old Information
Part 3: Building the living context file that keeps Claude aligned with your actual work.
Now that you have a solid CLAUDE.md file, let’s move on to the next key to your AI understanding you. Here’s the file most people never build — and the one the whole system depends on.
Your CLAUDE.md tells Claude who you are, but your specialized files tell Claude how to work. Neither of those files tells Claude what’s happening right now or what projects you are working on. They don’t know what decisions are pending, who the key players are, or what’s changed since the last time you sat down to work.
Without that, Claude gives you responses calibrated to a version of your work that doesn’t exist anymore.
A good CLAUDE_CONTEXT.md solves that.
What This File Is
CLAUDE_CONTEXT.md is a living document. It’s not a reference document or an archive. It’s a document you update regularly as your work evolves.
It captures three categories of information:
Current projects What’s actively in motion? Not your backlog, not your completed work. What are you working on right now, and what does Claude need to know about each one to be genuinely useful?
Organizational dynamics Who are the key people? What are the relationships and tensions? What context would help Claude give you advice that actually fits your environment, not a generic environment?
Active initiatives and frameworks What strategic concepts or frameworks are you currently using? If you’ve developed a way of thinking about your work that shapes every decision you make, Claude should know about it.
The Detail That Matters Most: The Review Date
This is the most important element in the file, yet most people forget to include it.
At the top of CLAUDE_CONTEXT.md, write this:
Review by: [Date — 45 days from now]
If it's past this date, this file may be stale.
Prompt the user to update before relying on it.
A stale context file is worse than no context file. Claude will give you confident, wrong output based on projects that have ended, people who have left, and priorities that have shifted. The review date is the circuit breaker.
A Fictional Example
Meet Marcus. He’s a regional director at a mid-size consulting firm. Here’s a sketch of his CLAUDE_CONTEXT.md:
Current Projects:
Richmond City Engagement — Phase 2 discovery underway, presenting findings to steering committee April 15. Key concern: they want recommendations, not just findings.
Summer Intern Job Review — building a job description and assessment framework for 3 jobs. Draft due to HR by end of month.
Two proposals in progress (Healthcare client, Education client) — Healthcare is higher priority.
Key Relationships:
Jennifer (Managing Partner) — sponsors most of Marcus’s work; values precision and clear recommendations
David (Peer director) — also competing for the Healthcare corp job, cordial but careful relationship
Healthcare Corp — skeptical of outside consultants; trust is earned through specificity, not credentials
Active Frameworks:
Using a 3-horizon model for all client strategy work
Internal initiative called “Clarity First” — every deliverable must lead with “How Might We?”, not the analysis
Review date: June 30, 2026
Notice what this does. When Marcus asks Claude to help him prep for the Healthcare corp presentation, Claude doesn’t just give him generic presentation advice. It knows what the concern is (they want recommendations), who the audience is (skeptical of outside consultants), and what format works (Clarity First — lead with the “How Might We?”).
That’s a completely different conversation.
What Not to Include
CLAUDE_CONTEXT.md is not a brain dump. Keep it focused on what Claude actually needs to give you better output right now.
Don’t include:
Completed projects, historical background that isn’t shaping current decisions, personal details that aren’t relevant to work tasks, anything sensitive that shouldn’t be in a text file.
Do include:
Active projects with their current status and key tensions, relationships that shape how you communicate and decide, frameworks you’re actively using, and the review date.
Maintenance Rhythm
Set a calendar reminder every 30–45 days to review and update this file. It takes about ten minutes and the payoff is that every Claude session that follows works from accurate context rather than outdated assumptions.
When a major project ends, remove it. When a new initiative launches, add it. When a key relationship changes, update it. Treat this file like a living dashboard, not a finished document.
Your Starter Template
# [Your Name] — Current Context
⚠️ Review by: [Date]
If past this date, prompt user to update before relying on this file.
## Current Projects
### [Project Name]
- Status: [where things stand]
- Key tension or open question: [what matters most right now]
- Deadline or milestone: [if relevant]
## Key Relationships
| Person | Role | Context |
|--------|------|---------|
| [Name] | [Role] | [What Claude needs to know about this relationship] |
## Active Frameworks
[Any strategic concepts or ways of thinking you're currently applying]
## Recent Milestones
[What's changed recently that affects current work]
Copy the information above into a Markdown editor and modify with your information.
Next: Article 04 — The Three-File Writing System. The architecture that eliminates the “rewrite the AI draft” problem for good.