← sources

Sharing projects context in the team

source: reddit (reddit:ClaudeCode)published 2026-10-11 21:20ingested 2026-10-12 02:39

retained text

We extensively use Claude Code for day to day task in our team. We are currently facing the following issues:  
\- As different engineers working in different projects, sometimes it becomes difficult to share what's the problem, what has been done so far and why, what to do next etc. 

\- Even in the same projects, while two engineers working in two different tasks and need help from each other, they need to setup a meeting to share what's the problem, what has been done so far, what's next etc. 

\- During the PR review, due to the lack of context, the reviewer needs either a meeting/slack discussion or bulky text description in the PR to make sure he/she understands what actually the Pr is for!

\- When an engineer works in a ticket, he/she does several steps for testing, validating, parity checking etc., which are sometimes very useful for other engineers to understand the problem better.

As context sharing is becoming hard day by day, killing a lot of time and making engineers frustrated. I know about writing docs in confluence etc. helps but I am looking for this functionality to be intrgrated in claude code so that if an engineer wants to know what's going on, he/she will be able to ask something like 'Tell me whats going on in ticket Y of project X?' and a summary will be provided along with the necessary docs etc. 

What are some of the better ways to share the knowledge among the team to make understanding context better? Is there anything in claude you use to share the context internally?

document fetched 2026-10-12 00:34 · canonical https://reddit.com/r/ClaudeCode/comments/1x3jusp/sharing_projects_context_in_the_team