Every article I publish on Substack is also released as an LLM-friendly markdown file in my In the Weeds GitHub repo. Today, I added the Team OS deep dive I did with Aakash Gupta.
The Team OS is a shared repo where your entire team checks in their work - structured so that any coding agent can find exactly what it needs to help any team member with the task at hand. The teams that set this up work together at a completely different level.
My goal is to get you started on setting up your own Team OS. Here's how.
Clone the repo, start a new Claude Code session inside it, and give Claude this prompt:
"Read through the Team OS article and then clone and explore the example repo linked in the article. Based on what you learn from both, help me plan a Team OS for my team. Start in plan mode. Ask me about my team structure, what tools we use, and what types of documents we work with. Then design the full system: a root claude.md with a doc index and team roster, folder-level claude.md files as navigation maps for each section, and a folder architecture tailored to how my team actually works."
Today’s the day to get started and uplevel how your team works together.