10h • 📚 Resources & Finds
ICM for Teams: Multiple Personal Repos + One Shared Repo Approach
This is an update on my first post here https://www.skool.com/cliefnotes/icm-for-teams-my-understanding-to-onboarding-coworkers-to-a-shared-content-pipeline?p=03813a63. And thanks to solid inputs by , i decided to do an update.
This is a more robust and scalable way to run a shared ICM content system with multiple people. It works especially well for teams.
Why This Approach?
- Everyone has their own private workspace, so there is no risk of stepping on each other's drafts.
- There is still one source of truth for the shared framework, rules, and client info.
- Merge conflicts are much less likely.
- It is easy to pick up someone's work if they are absent.
Overall Structure
The use two types of repositories.
- Shared Repo (one for the whole team)
Contains:
- Framework, rules, prompts, and stages
- Client information and brand guidelines
- Shared logs
Does not contain personal ideas or drafts.
2. Personal Repo (one for each person)
Contains:
- Your own `stage folder e.g 01-ideas`, `02-drafts`, `03-formats`, and working content
Fully private to you.
Step by Step Setup Guide
For You (The Person Who Built the Original System)
Step 1: Create the Shared Framework Repo
1. Create a new private GitHub repository e.g `marketing-content-framework`.
2. Copy only the framework files into it:
- `agent.md` / `CLAUDE.md`
- `context.md`
- Core stages and context contracts
- Brand guidelines, rules, templates
- Any shared client projects or logs folder
3. Add a `.gitignore`. Example:
```gitignore
# Ignore personal content folders
01-ideas/
02-drafts/
03-formats/
*.local.md
```
4. Push it to GitHub.
Step 2: Create Your Personal Repo
1. Create another private repo e.g `yourname-content-workspace`.
2. Clone the shared framework into it, or copy the structure.
3. This becomes your main working folder.
For Your Teammates
Step 1: Set Up Your Personal Workspace
1. Install Git (one time).
2. Create their own private GitHub repo: e.g `name-content-workspace`.
3. Clones their new empty repo to your computer.
4. Clones the Shared Framework repo: E.g
```bash
```
5. Copy the contents of the framework folder into their personal workspace, or use symlinks if advanced.
6. Now they have the full system with the latest shared rules.
Step 2: Daily Work e.g Content creation
- Work inside your personal repo.
- Talk to your AI agent normally. For example:
- "Generate 5 LinkedIn ideas about [topic]"
- "Turn idea #3 into a full draft"
- "Format this draft for Instagram carousel and Substack"
- All your work stays in your personal repo.
Step 3: Get Framework Updates
When the shared framework is updated, pull the latest version using one of these options.
1. Easiest: ask the agent, "Update my framework from the shared repo."
2. Manual: run this command in the framework folder:
```bash
cd framework
git pull
```
Step 4: Share Improvements Back
If you improve a prompt or stage:
1. Work on it inside the framework folder.
2. Ask the agent: "Create a Pull Request to update the shared framework with my carousel improvement."
3. The content lead reviews and merges it into the Shared Repo.
Step 5: Sharing Finished Content
- Save final approved posts to the teams Google Drive.
Benefits of This Approach
- Zero merge conflicts on personal content.
- Everyone always works from the latest shared framework.
- Easy for the team lead to check progress or pick up work.
- Scalable as the team grows.
- Your personal drafts remain private and safe.
7
4 comments
ICM for Teams: Multiple Personal Repos + One Shared Repo Approach
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
🔥
+1699
2
🔥
+1670
3
+1251
4
+971
5
+620
Powered by