← Stash
← All posts

Claude for Project Managers: Persistent Project Knowledge That Travels With You

June 2026 · 6 min read

Project managers know things. You know why the launch date slipped in March. You know which stakeholder actually makes the call versus who just needs to be informed. You know the vendor contract was extended to Q4 but only if the scope stays below a certain threshold. You know the decision about the API design was contested and documented in a Confluence page nobody will ever find again.

You know all of this. Claude doesn't.

Every time you start a new conversation with Claude for help on a project — drafting a status update, preparing for a stakeholder call, unblocking a team member — you have to reload it with everything it needs to actually be useful. That's 5–10 minutes of briefing before you can do the thing you actually wanted to do.

Stash eliminates that. It gives Claude a persistent, searchable store of project knowledge that lives outside any one conversation. Set it up once. From then on, Claude already knows your projects.

What project knowledge is worth storing

Not everything — you don't want to dump your Jira board into Stash. The records worth storing are the ones that aren't in any system, or that are in a system nobody will actually search:

CategoryWhat to store
Stakeholder contextWho makes decisions vs. who needs to be informed; communication preferences; political sensitivities
Key decisionsWhat was decided, who decided it, why — especially the "we almost went a different way" reasoning
Blockers & dependenciesWhat's waiting on whom, since when, and what the risk is if it drags
Scope boundariesWhat's explicitly in or out; what was argued about and settled
Vendor / third-party contextRelationship notes, contract constraints, escalation paths
Risk register (informal)The risks you're watching but haven't formally escalated

The pattern: capture once, query forever

After any meeting, decision, or discovery worth remembering, you take 30 seconds to tell Claude to save it. Example:

"Save to Stash: Project Atlas — CTO approved moving the API deadline to July 12th but only if we drop the reporting dashboard from scope. This was agreed in the 4 Jun steering group. Sarah (CTO) and Marcus (head of product) were in the room."

That's it. Now that context is retrievable in any future conversation — next week's steering prep, a new team member's onboarding, a status update email three months from now.

This isn't your Jira board. Stash holds the context that isn't in any formal system: the soft agreements, the reasoning behind decisions, the stakeholder dynamics. Think of it as the notes you'd give a new PM taking over your projects.

A real session: preparing for a stakeholder call

PM
I have a steering group call on Project Atlas in 20 minutes. What do I need to know going in?
Claude (querying Stash)
Found 11 records on Project Atlas. Key things for this call:

Open item: Marcus still hasn't confirmed the reporting dashboard drop — it's been 6 days since the CTO approved it. He may push back today.
Risk: Vendor (DataCo) contract renewal is due in 3 weeks; no one has started the paperwork yet
Political note: Sarah (CTO) wants to be asked before any scope change is communicated to the board — she said this explicitly in April
Timeline: July 12 API deadline is firm. Everything downstream moves if that slips.
Unresolved: QA resource sharing with the platform team — platform says they're at capacity until end of July
PM
Good. Help me prepare a two-minute opening update that flags the DataCo renewal without alarming anyone.
Claude
Sure — keeping the DataCo note matter-of-fact and framing it as a near-term action rather than a risk: [draft follows]

20 minutes of preparation compressed to 2. And Claude had the right context without you saying a word about the project history.

Managing multiple projects

Stash is especially useful if you're running more than one project at the same time — which most PMs are. You can keep records organized by project name, and search across them with natural language.

Instead of hunting through meeting notes from six weeks ago or trying to remember which Slack thread had the decision, you ask Claude: "What decisions have we made about vendor contracts across all my projects?" and it surfaces the relevant records instantly.

Onboarding a new team member

This is an underrated use case. When a new developer, designer, or PM joins a project, the knowledge transfer is usually ad hoc and lossy. The context that lives in one person's head gets summarized in a single kickoff call, mostly forgotten by the next week.

If your project knowledge is in Stash, you can point a new team member at it — or ask Claude to pull together an onboarding summary:

"Summarize everything in Stash about Project Atlas that a new team member should know in their first week."

Claude searches the store and produces a structured briefing. No preparation required on your end. The institutional knowledge that used to live only in your head is now retrievable by anyone you give access to.

What Stash is not

Stash doesn't replace your project management tool. It doesn't track tasks, manage sprints, or generate Gantt charts. What it does is hold the surrounding context — the knowledge that makes your PM tool meaningful — in a form Claude can access and reason about.

Think of it as the project bible you always meant to write but never had time for, made queryable by AI.

Getting started

In Claude, go to Settings → Connectors and add:

https://app.stashlite.com/mcp

Sign in with Google. Your account is created automatically. Start adding project records in any conversation — Claude saves them and can retrieve them in any future session.

Free tier: 2,500 records, 50 queries/month. Most PMs hit the 50-query limit before the record limit — because once it works, you use it constantly. The paid tier is £8/month and removes both caps. Pricing may change; cancel anytime.

Give Claude a permanent project memory

30 seconds to connect. Saves hours of re-briefing.

https://app.stashlite.com/mcp Get your connector URL →