How to run AI-SHIPR across a VP and multiple PMs using a shared cloud drive. Three sections: shared concepts that apply to any cloud provider, then a full guide for Google Drive, and one for Microsoft 365.
🗂
Section 1
Shared Information
01
Why a Shared Cloud Drive
AI-SHIPR runs on local files. Claude Code reads from a folder on your machine — which means every team member needs access to the same files from their own computer.
A shared, organisation-owned cloud drive (not personal storage) is the right tool because it mounts at a consistent path on every machine. All members see the same folder structure at the same relative path — so Claude's file references work identically for everyone.
Personal storage does not work — it includes the username or company name in the path, which differs per machine.
Use Google Shared Drive (not My Drive) or SharePoint Team Site (not OneDrive personal). Both are org-owned and mount at a consistent path regardless of who is logged in.
02
Folder Structure
AI-SHIPR-ORG/← root of the shared drive vp/← VP's full AI-SHIPR workspace shared/← GLOBAL LAYER — VP writes, all PMs read Vision.md Strategy.md OKRs.md Strategic-Bets.md Portfolio-Roadmap.md Constraints.md R-Relationships/Team/← Roster, PM profiles, 1:1 logs Settings.md← team_mode: lead CLAUDE.md A-AI/← includes Portfolio-Strategist + Team-Manager Learning.md pm-alice/← Alice's full AI-SHIPR workspace CLAUDE.md← reads ../vp/shared/ first, then local Settings.md← team_mode: individual S-Strategy/← Alice's product strategy H-Hypotheses/ I-Initiatives/ P-Proof/ R-Relationships/ I-Information/ A-AI/ Learning.md pm-bob/← same structure as pm-alice ...
The ownership rule: Only the VP writes to vp/shared/. Each PM writes only to their own folder. No PM edits another PM's folder or the shared layer.
03
The One Rule
The entire system works conflict-free as long as one rule holds:
No PM ever edits vp/shared/
Only the VP writes to the global layer. PMs read it. PMs write only to their own folder.
Cloud drive permissions (Viewer / read-only on vp/shared/) enforce this technically. But communicating it explicitly to the team matters too — the structure should be understood, not just imposed.
When the VP updates vp/shared/OKRs.md, every PM gets the updated OKRs in their next Claude session automatically. No distribution needed. No manual copy-paste. This is the compounding effect the structure enables.
🟢
Section 2
Google Drive Setup
01
Why Google Shared Drive
Google Shared Drive (not a personal Drive) is the right tool because it mounts at a consistent path on every machine via Google Drive for Desktop. All members see the same folder structure at the same relative path — so Claude's file references work identically for everyone.
Personal Google Drive does not work for this — it includes the username in the path, which differs per machine.
Use Google Workspace Shared Drive, not "My Drive". Shared Drives are organization-owned and mount at a consistent path regardless of who is logged in.
02
VP Setup
1
Create the Shared DriveIn Google Drive, click Shared drives in the left sidebar → New → name it AI-SHIPR-ORG (or your company name). This creates the organization-owned root.
2
Download and install Google Drive for DesktopDownload from drive.google.com/drive/download. Install, sign in with your Google Workspace account. The Shared Drive will appear on your machine as a mounted drive.
3
Create the VP folder and download AI-SHIPRInside the Shared Drive, create a vp/ folder. Download your AI-SHIPR zip, extract it into vp/. This is your complete AI-SHIPR instance.
4
Create the shared/ subfolderInside vp/, create a folder called shared/. This is the global layer. Create these files inside it: Vision.md, Strategy.md, OKRs.md, Strategic-Bets.md, Portfolio-Roadmap.md, Constraints.md. Fill them in with your organization's current strategy.
5
Enable Lead Mode in Settings.mdOpen vp/Settings.md and set:team_mode: leadThis activates the Portfolio-Strategist and Team-Manager agents.
6
Add the team reading instruction to CLAUDE.mdAt the top of the Session Start Protocol in vp/CLAUDE.md, add:Before reading local files, read all PM folders under ../pm-*/S-Strategy/
for portfolio context. Then read shared/ for global strategy.
7
Open Claude Code from your VP folderIn Terminal (Mac) or Command Prompt (Windows), navigate to your VP folder and launch Claude:Mac: cd ~/Google\ Drive/Shared\ drives/AI-SHIPR-ORG/vp && claude
Windows: cd "G:\Shared drives\AI-SHIPR-ORG\vp" && claude
03
Each PM's Setup
1
Accept the Shared Drive invitationThe VP invites each PM to the Shared Drive with the right permissions (see Section 05). Accept the invitation — the AI-SHIPR-ORG drive will appear in your Google Drive.
2
Download and install Google Drive for DesktopDownload from drive.google.com/drive/download. Install and sign in. The Shared Drive will mount automatically on your machine.
3
Locate your personal folder on the mounted driveYour folder already exists — the VP created it for you. Navigate to it:Mac: ~/Google Drive/Shared drives/AI-SHIPR-ORG/pm-[yourname]/
Windows: G:\Shared drives\AI-SHIPR-ORG\pm-[yourname]\
4
Download AI-SHIPR and extract it into your folderThe VP will send you the AI-SHIPR zip. Extract it into your pm-[yourname]/ folder. Do not extract it anywhere else — the relative paths in CLAUDE.md depend on being inside the Shared Drive structure.
5
Add the global strategy reading instruction to your CLAUDE.mdAt the top of the Session Start Protocol in your CLAUDE.md, add this line before the local file reads:Before reading local files, read ../vp/shared/ for org-level strategy,
OKRs, and portfolio direction. These take precedence over
individual product decisions.
6
Set team_mode to individual in Settings.mdOpen your Settings.md and confirm:team_mode: individualThis keeps the lead-mode agents (Portfolio-Strategist, Team-Manager) inactive for PMs.
7
Fill in your Setup Worksheet and run Populate StrategyOpen Setup-Worksheet.md in your folder and answer the questions about your product. Then in Claude Code, run:Run Populate Strategy based on the Setup Worksheet I filled inClaude will generate your product strategy files, automatically aligned with the org-level strategy it read from ../vp/shared/.
8
Open Claude Code from your PM folder to workMac: cd ~/Google\ Drive/Shared\ drives/AI-SHIPR-ORG/pm-[yourname] && claude
Windows: cd "G:\Shared drives\AI-SHIPR-ORG\pm-[yourname]" && claudeAlways launch Claude Code from your own folder — not from the root or another PM's folder.
04
Mapping Google Drive on Your Machine
1
Download Google Drive for DesktopGo to drive.google.com/drive/download and download the Mac version.
2
InstallOpen the downloaded .dmg file and drag Google Drive to your Applications folder. Launch it.
3
Sign in with your Google Workspace accountA browser window will open. Sign in — use the same account the VP invited to the Shared Drive.
4
Choose streaming mode (recommended)In Google Drive preferences, set sync to Stream files — files stay in the cloud and sync on access. This prevents filling your local disk.
5
Find the Shared Drive on your MacOpen Finder. In the sidebar under Locations, you will see Google Drive. Inside it, open Shared drives → AI-SHIPR-ORG. Your full path:~/Google Drive/Shared drives/AI-SHIPR-ORG/
6
Verify the path in Terminalls ~/Google\ Drive/Shared\ drives/AI-SHIPR-ORG/You should see vp/ and the PM folders listed.
1
Download Google Drive for DesktopGo to drive.google.com/drive/download and download the Windows installer.
2
InstallRun the installer (.exe). It will install and launch automatically. Sign in with your Google Workspace account.
3
A new drive letter appearsGoogle Drive is assigned a drive letter (default: G:). It appears in File Explorer under This PC. You can change the letter in Google Drive settings if needed.
4
Find the Shared DriveOpen File Explorer → G:\ → Shared drives → AI-SHIPR-ORG. Your full path:G:\Shared drives\AI-SHIPR-ORG\
5
Verify in Command Promptdir "G:\Shared drives\AI-SHIPR-ORG"You should see vp and the PM folders listed.
6
Note for Claude Code paths on WindowsWhen launching Claude Code, use the full Windows path with the drive letter:cd "G:\Shared drives\AI-SHIPR-ORG\pm-[yourname]"
claude
05
Permissions
Role
Shared Drive access
Folder write access
Read access
VP Product
Manager
vp/ including shared/
All PM folders + vp/shared/
Each PM
Contributor
Their own pm-[name]/ only
Their own folder + vp/shared/
Permission Setup — Step by Step
1
Add the VP as Manager of the Shared DriveIn the Shared Drive → Manage members → add VP email → role: Manager. Managers can add members and set folder-level permissions.
2
Add each PM as Contributor to the Shared DriveIn the Shared Drive → Manage members → add PM email → role: Contributor. Contributors can edit files in folders they have access to.
3
Restrict each PM to their own folder onlyRight-click each pm-[name]/ folder → Share → add only that PM → role: Contributor. They will not see other PM folders unless explicitly shared.
4
Share vp/shared/ as read-only with all PMsRight-click vp/shared/ → Share → add all PM emails → role: Viewer. PMs can read but not edit the global strategy files.
5
Keep the rest of vp/ privateDo not share the rest of vp/ (1:1 logs, PM profiles, VP learning log) with PMs. Those stay VP-only.
Important: Google Drive folder-level permissions are only available in Shared Drives (not personal My Drive). This is another reason Shared Drive is required for this setup.
🔵
Section 3
Microsoft 365 Setup
01
Why SharePoint
If your organisation runs on Microsoft 365, use SharePoint instead of Google Shared Drive — not OneDrive personal. OneDrive personal has the same path problem as Google My Drive. SharePoint is organisation-owned, shared across the team, and mounts locally through the OneDrive sync client that is already installed on most Windows machines.
Concept
Google
Microsoft
Org-owned shared folder
Shared Drive
SharePoint Team Site
Sync client
Google Drive for Desktop
OneDrive (built into Windows, free on Mac)
Mac path
~/Google Drive/Shared drives/AI-SHIPR-ORG/
~/OneDrive - [Company]/AI-SHIPR-ORG/
Windows path
G:\Shared drives\AI-SHIPR-ORG\
C:\Users\...\OneDrive - [Company]\AI-SHIPR-ORG\
Folder permissions
Drive UI → Share → Viewer / Contributor
SharePoint UI → Share → View / Edit
The folder structure, ownership rules, and CLAUDE.md instructions are identical to the Google Drive setup. The only difference is the sync client and the local path format.
02
VP Setup
1
Create a SharePoint Team SiteIn Microsoft 365, go to SharePoint → + Create site → Team site. Name it AI-SHIPR-ORG (or your company name). This creates the organisation-owned root, equivalent to a Google Shared Drive.
2
Create the folder structure in the Documents libraryInside the site's Documents library, create the vp/ folder and all pm-[name]/ folders. Extract the AI-SHIPR zip into vp/. Create the vp/shared/ subfolder and fill in the strategy files.
3
Sync to your local machineIn SharePoint, open the Documents library → click Sync. The OneDrive app opens and begins syncing the site to your machine. The folder appears in Finder / File Explorer under OneDrive – [Company Name].
4
Set permissionsIn SharePoint, right-click each folder → Share → set View / Edit access per role. The VP has Edit on all. Each PM has Edit on their own folder only, View on vp/shared/.
5
Enable Lead Mode and open Claude CodeOpen vp/Settings.md, set team_mode: lead. Then launch Claude from your VP folder:Mac: cd ~/OneDrive\ -\ [Company]/AI-SHIPR-ORG/vp && claude
Windows: cd "C:\Users\[you]\OneDrive - [Company]\AI-SHIPR-ORG\vp" && claude
03
Each PM's Setup
1
Accept the SharePoint site invitationThe VP invites each PM to the SharePoint site via email. Accept the invitation — the site becomes accessible in your Microsoft 365 account.
2
Install OneDrive (Mac only — already built into Windows)On Mac, download OneDrive from the App Store or from microsoft.com/onedrive. Sign in with your Microsoft 365 account.
3
Sync the SharePoint folder to your machineOpen the SharePoint site in the browser → Documents → click Sync. The folder syncs locally and appears under OneDrive – [Company Name].
4
Navigate to your PM folder and extract AI-SHIPRMac: ~/OneDrive - [Company]/AI-SHIPR-ORG/pm-[yourname]/
Windows: C:\Users\[you]\OneDrive - [Company]\AI-SHIPR-ORG\pm-[yourname]\Extract the AI-SHIPR zip into this folder. Update CLAUDE.md and Settings.md exactly as in the Google Drive guide (PM Setup, Steps 5–6) — the instructions are identical.
5
Open Claude Code from your PM folderMac: cd ~/OneDrive\ -\ [Company]/AI-SHIPR-ORG/pm-[yourname] && claude
Windows: cd "C:\Users\[you]\OneDrive - [Company]\AI-SHIPR-ORG\pm-[yourname]" && claude
04
Permissions
Role
Site access
Folder write access
Read access
VP Product
Site Owner / Edit
vp/ including shared/
All PM folders + vp/shared/
Each PM
Edit (folder-scoped)
Their own pm-[name]/ only
Their own folder + vp/shared/ (View)
Note: SharePoint folder-level permissions require breaking permission inheritance. Right-click the folder → Manage access → Stop inheriting permissions, then set the specific access. This is the equivalent of Google Drive's per-folder sharing.
The relative path still works. The company name appears in the absolute path (OneDrive - Acme Corp), so it differs between organisations. But all relative paths inside the folder — ../vp/shared/ — resolve identically regardless of what comes before them. Nothing in CLAUDE.md needs to change between Google and Microsoft setups.
🔷
Section 4
Atlassian Confluence Setup
01
Why Confluence is Different
Confluence is a wiki and documentation platform, not a file system. Unlike Google Drive or SharePoint, it does not mount as a local folder on your machine — so Claude Code cannot read Confluence pages directly as local files.
The right approach is a hybrid model: Confluence serves as your team's living documentation layer — strategy pages, decisions, retrospectives — while AI-SHIPR's local files remain the source that Claude Code reads. The two stay in sync through a simple export step.
Layer
Tool
Who reads it
Team knowledge base
Confluence Space
Humans — VP, PMs, stakeholders
AI-SHIPR working files
Local drive (Google / SharePoint / local)
Claude Code
When the VP updates the OKRs page in Confluence, they also update vp/shared/OKRs.md. The Confluence page is for the team to read; the .md file is for Claude. Both take 30 seconds to keep in sync.
02
Space Structure
AI-SHIPR Space (Confluence) Shared Strategy← VP writes, all PMs view Vision Strategy OKRs Strategic Bets Portfolio Roadmap Constraints VP Workspace← VP only Team Roster 1:1 Notes PM Profiles PM Workspaces PM Alice← Alice edits, VP views PM Bob← Bob edits, VP views ...
Mirror the AI-SHIPR folder structure in Confluence page names. When a page and a local file share the same name (e.g., OKRs), it is trivial to keep them in sync.
03
VP Setup
1
Create the Confluence SpaceIn Confluence, click Spaces → Create space → Blank space. Name it AI-SHIPR (or your product org name). Set it as a team space so it is visible to all invited members.
2
Create the Shared Strategy sectionUnder the space home, create a parent page called Shared Strategy. Under it, create child pages: Vision, Strategy, OKRs, Strategic Bets, Portfolio Roadmap, Constraints. Fill them in with your current strategy content.
3
Create a local drive alongside ConfluenceSet up your AI-SHIPR local folder using Google Drive, SharePoint, or a local path as described in Sections 2–3. Confluence does not replace the local files — it is the human-readable companion. Paste the strategy content from Confluence into the corresponding .md files in vp/shared/.
4
Add a sync reminder to your workflowAt the top of vp/CLAUDE.md, add a note so Claude reminds you:After updating any file in vp/shared/, remind me to update the
corresponding Confluence page in the Shared Strategy section.
5
Invite the teamGo to Space Settings → Permissions. Add each PM with View access to the full space. Individual page-level restrictions (below) will limit write access to the right sections.
04
Each PM's Setup
1
Accept the space invitationThe VP invites each PM to the Confluence space. Accept — the AI-SHIPR space will appear in your Confluence sidebar under Spaces.
2
Read the Shared Strategy pagesNavigate to Shared Strategy and read Vision, OKRs, and Constraints before starting any planning work. These are the same documents Claude reads from ../vp/shared/ — Confluence is the human layer for the same content.
3
Create your PM Workspace sectionUnder PM Workspaces, create a parent page with your name (e.g., PM Alice). Create child pages that mirror your AI-SHIPR folders: Strategy, Initiatives, Hypotheses, Decisions. Keep these in sync with your local .md files.
4
Set up your local AI-SHIPR folderFollow the Google Drive or SharePoint PM setup (Sections 2–3) to get your local folder running. Confluence is the companion layer — Claude Code reads from the local files, not from Confluence.
5
Sync key outputs back to ConfluenceWhen Claude generates significant output — a strategy doc, a decisions summary, a roadmap — paste the result into the corresponding Confluence page. This keeps Confluence useful for stakeholders who do not use Claude Code.
05
Permissions
Role
Space access
Page edit access
Read access
VP Product
Space Admin
All pages
All pages
Each PM
View + Edit (page-scoped)
Their own PM Workspace section only
Shared Strategy + their own section
Permission Setup — Step by Step
1
Set space-level View access for all PMsSpace Settings → Permissions → add each PM with Can view. This gives read access to the whole space by default.
2
Restrict the Shared Strategy section to VP edit onlyOpen the Shared Strategy parent page → ⋯ More actions → Page restrictions → set Edit: VP only. PMs will be able to read but not modify strategy pages.
3
Give each PM Edit access to their own sectionOpen each PM's parent page → Page restrictions → Edit: that PM + VP. This mirrors the folder-level permissions in Google Drive and SharePoint.
4
Keep VP Workspace restrictedSet the VP Workspace parent page restriction to View + Edit: VP only. 1:1 notes and PM profiles stay private.
Cloud vs. Data Center: Page restrictions work the same way in Confluence Cloud and Confluence Data Center. In Data Center, Space Administrators can also manage permissions via group membership in addition to individual users.
Confluence as the human layer, local files as the AI layer. The VP updates OKRs.md in the shared folder → Claude reads it → the VP also updates the OKRs Confluence page → the team reads it. Two steps, same information, right tool for each audience.