Team Setup with Cloud

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.

The entire system works conflict-free as long as one rule holds:

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.

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.

• 1
  Create the Shared Drive In 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 Desktop Download 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-SHIPR Wizard route: skip. Unzip AI-SHIPR-ORG/ straight into the Shared Drive; vp/ is already inside it with the framework in place. Manual route: inside the Shared Drive, create a vp/ folder. Download your AI-SHIPR zip, extract it into vp/. This is your complete AI-SHIPR instance.
• 4
  The shared/ layer Inside vp/, shared/ is the global layer and holds six files: Vision.md, Strategy.md, OKRs.md, Strategic-Bets.md, Portfolio-Roadmap.md, Constraints.md. You do not write these by hand. Running Populate-Strategy on your filled Setup Worksheet generates all six. Review what it produces, and run OKR-Partner on OKRs.md before the team reads it, since the worksheet collects metrics and bets rather than formal OKRs.
• 5
  Enable Lead Mode in Settings.md Open vp/Settings.md and confirm (the wizard sets this for you): team_mode: lead This activates the Portfolio-Strategist and Team-Manager agents.
• 6
  Nothing to add to CLAUDE.md Earlier versions asked you to paste a reading instruction into vp/CLAUDE.md by hand. That is no longer needed. The framework's Session Start protocol branches on team_mode by itself: in lead it reads shared/, every ../pm-*/S-Strategy/ for the portfolio view, and R-Relationships/Team/, before any local file. If you added that line to an older install, leave it or delete it. It is a duplicate now, not a conflict.
• 7
  Open Claude Code from your VP folder In 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

• 1
  Accept the Shared Drive invitation The 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 Desktop Download 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 drive Your 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
  Check your folder, or extract into it Wizard route: nothing to download. Your pm-[yourname]/ folder already holds the framework, a pre-set Settings.md and a personal START-HERE.md. Open that file and follow it. Do not ask for a separate framework zip; installing one on top overwrites your setup. Manual route: the lead sends you the AI-SHIPR zip. Extract it into your pm-[yourname]/ folder. Do not extract it anywhere else - the relative paths depend on sitting inside the Shared Drive structure, and a copy in your Downloads folder cannot see ../vp/shared/. It will not error, it will just answer without your org's strategy.
• 5
  Nothing to add to CLAUDE.md Earlier versions asked you to paste a reading instruction in by hand. The framework now does it from team_mode: in individual it reads ../vp/shared/ before any local file and flags anything in your strategy that conflicts with the org layer.
• 6
  Set team_mode to individual in Settings.md Open your Settings.md and confirm (the wizard sets this for you): team_mode: individual This keeps the lead-mode agents (Portfolio-Strategist, Team-Manager) inactive for PMs.
• 7
  Fill in your Setup Worksheet and run Populate Strategy Open 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 in Claude 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 work Mac: cd ~/Google\ Drive/Shared\ drives/AI-SHIPR-ORG/pm-[yourname] && claude Windows: cd "G:\Shared drives\AI-SHIPR-ORG\pm-[yourname]" && claude Always launch Claude Code from your own folder - not from the root or another PM's folder.

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.

• 1
  Create a SharePoint Team Site In 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 library Inside the site's Documents library, create the vp/ folder and all pm-[name]/ folders. Wizard route: already done, just unzip your download here. Manual route: extract the AI-SHIPR zip into vp/. Create the vp/shared/ subfolder and fill in the strategy files.
• 3
  Sync to your local machine In 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 permissions In 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 Code Open 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

• 1
  Accept the SharePoint site invitation The 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 machine Open 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-SHIPR Mac: ~/OneDrive - [Company]/AI-SHIPR-ORG/pm-[yourname]/ Windows: C:\Users\[you]\OneDrive - [Company]\AI-SHIPR-ORG\pm-[yourname]\ Wizard route: already done. Manual route: 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 folder Mac: cd ~/OneDrive\ -\ [Company]/AI-SHIPR-ORG/pm-[yourname] && claude Windows: cd "C:\Users\[you]\OneDrive - [Company]\AI-SHIPR-ORG\pm-[yourname]" && claude

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 mirror model: Confluence is where people edit, a small local folder is what Claude reads, and one sync command pulls the first into the second. vp/shared/ becomes a per-machine cache instead of a mounted folder. AI-SHIPR itself needs no changes - ../vp/shared/ still resolves, and the session-start read is still a plain file read that works offline.

Sync in one direction only, and key it on page IDs. One editing surface, one source of truth. Maintaining the wiki page and the .md file separately looks cheap - thirty seconds each - but they drift, and within a month nobody knows which copy is true. Keying on IDs rather than page titles matters because renaming a page is normal behaviour and must never silently orphan a file.

A page called PM Alice assumes the person outlasts the product. In practice it is the other way round. Three kinds of content live for three different lengths of time:

Person-keyed pages give the middle row the wrong lifetime. When Alice leaves, years of product reasoning sits inside a page named after someone who no longer works there.

Reallocation breaks it before departure does. Alice owns two products above. The day Billing Portal moves to Bob, a page called PM Alice has to be surgically split and every inbound link rechecked. Keyed by product, that same reorg is one property change on one page. Reorgs are far more common than resignations, so this is the case that bites first.

The rule: churn should be a property change, not a page move. Give each product page these properties, and let page permissions follow Owner so a handover is one field rather than a permissions rebuild.

• 1
  Create the Confluence Space In 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 section Under 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 Confluence Set 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 workflow At 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 team Go 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.

• 1
  Accept the space invitation The 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 pages Navigate 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 a page for each product you own Under Product Workspaces, create one parent page per product (e.g., Scheduling Assistant), not one page named after you. Set Owner to yourself. 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 folder Install AI-SHIPR into pm-[name]/ and run bash setup.sh once. Claude Code reads the local files, never Confluence directly.
• 5
  Run the sync to populate vp/shared/ This pulls the six Shared Strategy pages down into your local mirror. Re-run it whenever the VP says the org context moved. Never hand-edit vp/shared/ - the next sync overwrites it.
• 6
  Publish upward before each reconciliation Paste your Vision, Strategic Bets and Personas into the product page you own, so the VP can read across the team. This is a deliberate copy-paste, not a sync - see Team Rollout, Phase 3.

AI-SHIPR runs on local files. At session start, Claude Code reads a fixed list of files in a fixed order - with team_mode: individual that list begins with ../vp/shared/. That guaranteed read is the whole mechanism. It is why org context compounds instead of being pasted into prompts by hand.

Google Drive and SharePoint were never the point. They were one way to make those paths resolve identically on every machine. Notion has no file path at all - there is no way for Claude Code to read a Notion page the way it reads a file.

Replacing the file read with a live Notion lookup means swapping a guaranteed read for a search: it costs tokens every session, adds latency, and breaks offline. So Notion can absolutely be the shared surface. It cannot be the runtime.

Every org page needs an Owner and a Last reviewed value, and in Notion those are database properties. Loose pages cannot carry them, which quietly kills the staleness check before you have written a line of content.

Add a Sync-Context skill to the shared repo so every machine gets it on clone. It reads a page-ID map, fetches each page, and writes the markdown mirror.

• 1
  Read the page-ID mapA Context-Index.md file in the repo root, mapping page ID to target filename. If it is missing, stop - never fall back to searching Notion by page name.
• 2
  Fetch each page by IDThrough the Notion connector. If a fetch fails, report it and continue - never write a partial or empty file over a good one.
• 3
  Flatten to markdown and write front matterCarry page_id, owner, last_reviewed and today's sync date into each file.
• 4
  Report, and flag two conditions loudlylast_reviewed older than 90 days is stale context. An empty owner is unowned context - the worse of the two, and usually means a PM left and the product was never reassigned.

• 1
  Create the Product Context teamspaceThen the Org Context database with the three properties above, and its six rows.
• 2
  Fill in the org contextThis is the part that actually matters. The plumbing is easy; the content is the work.
• 3
  Set permissionsView-only for the team on Org Context and Templates. See Section 5.06.
• 4
  Create the Product Workspaces databaseOne row per product, with Owner set to the PM who runs it.
• 5
  Record the page IDsAdd each ID and its target filename to Context-Index.md in the repo, and commit.
• 6
  Set team_mode: leadIn your own Settings.md.

• 1
  Clone the shared repoIt holds the AI-SHIPR runtime, the templates, Context-Index.md and the Sync-Context skill.
• 2
  Install AI-SHIPR into pm-[name]/Run bash setup.sh once, and confirm team_mode: individual in Settings.md.
• 3
  Connect the Notion connector in Claude CodeEach machine authenticates separately. Notion's own permissions decide what each person can see.
• 4
  Run /sync-contextThis populates your local vp/shared/ mirror. Re-run it whenever the VP says the org context moved.
• 5
  Then fill your Setup WorksheetIn that order, on purpose - see the tip below.