Project context that every agent on the project shares
Specs, decisions and context live side by side per project, so every assistant working on it starts from the same facts.
Who it’s for: Project leads, delivery teams and agencies running several client projects at once.
Context goes missing between tools
A project’s context is spread across tickets, chat threads and meeting notes. Every assistant someone opens starts from zero, and people paste the same background into each new conversation.
One repository per project
Keep a repository for the project, or a folder per project in a shared one, with the brief, the specs, the decisions and the open questions in Markdown. Anyone assigned to the repository can connect it to the assistant they already use.
Because access is granted per repository, a project can be shared with exactly the people on it, each signing in with their own account.
Decisions stay traceable
When a decision changes, update the note and commit it. Assistants read the branch as it is on your git host, and the audit log shows which notes were read, by whom, and from which client.
How to structure the repository
- Keep decisions as short numbered records: what was decided, why, and what was ruled out. A numbered decision is easy for an assistant to cite and easy for people to supersede.
- Separate what is settled (specs, decisions) from what is not (open questions). Asked for the state of the project, the assistant can tell the two apart.
- Keep a glossary of the client’s own terms, so drafts use their language rather than a guess.
Setting it up
-
Step 1: Create one repository per project, or a folder per project in a shared repository if the same people work on all of them.
-
Step 2: Assign the repository to the people on the project. Access is granted per repository, so a client’s project stays visible only to its team.
-
Step 3: Each person adds the endpoint to the assistant they use. Claude, ChatGPT and IDEs read the same files.