You need: A Claude Pro subscription ($20 USD/month) from claude.ai

1. Install Git

Windows: Download from git-scm.com/downloads/win - default options, just click through.

Mac: xcode-select --install (or brew install git if you have Homebrew).

Linux: sudo apt install git (Debian/Ubuntu) or sudo dnf install git (Fedora).

2. Install Claude Code

Windows (PowerShell):

irm https://claude.ai/install.ps1 | iex

Mac/Linux (Terminal):

npm install -g @anthropic-ai/claude-code

(Requires Node.js - download the LTS version if you don’t have it.)

“Not in your PATH” error? (Windows)

  1. Win + R → type sysdm.cpl → Enter
  2. Advanced tab → Environment Variables
  3. Select Path under User variables → Edit → New
  4. Paste the path it told you (e.g. C:\Users\YourName\.local\bin)
  5. OK everything → restart PowerShell

3. Authenticate

claude

It opens a browser. Sign in, then untick “contribute to training data”.

Type /exit to quit for now.

4. Clone the Template

git clone https://hedwards.dev/ccot ~/Files
cd ~/Files
git remote rename origin template
chmod +x .claude/scripts/*.sh

~/Files is your vault — everything lives here. The remote rename lets /update pull future template improvements.

4.5. Configure Environment

Mac/Linux — add to ~/.bashrc (Linux) or ~/.zshrc (Mac):

export VAULT_PATH="$HOME/Files"
alias cc='cd ~/Files && claude'

Then reload: source ~/.bashrc (or source ~/.zshrc).

Windows (PowerShell):

# Run once:
[Environment]::SetEnvironmentVariable("VAULT_PATH", "$HOME\Files", "User")
# Add to $PROFILE for the alias:
function cc { Set-Location ~/Files; claude }

Now you can type cc from anywhere to launch Claude Code in your vault.

5. Personalise

cc

(Or cd ~/Files && claude if you haven’t reloaded your shell yet.)

Type exactly:

I’ve just cloned this CCO template for my business. Help me personalise CLAUDE.md for my situation and walk me through the system.

Claude will interview you about your business, then write your CLAUDE.md.

6. Install Obsidian

Stay in the same Claude session. Type:

Download and install Obsidian, then open ~/Files as a vault.

7. Seed Your Vault

Still the same session. Work through these one at a time:

Write a deeper context file (clients, team structure, workflows - the stuff CLAUDE.md didn’t cover):

I want to create a detailed context file about my business operations. Ask me questions one at a time, then write it up in 07 System/.

Start a real project:

/start-project

Pick something you’re actually working on right now.

Capture a process from your head:

I’m going to describe how we onboard a new client. Ask me questions one at a time, then write it up as an SOP in the right folder.

Save your session:

/park

8. Tomorrow

Open your terminal, type cc, then:

/pickup

Everything from today is there. That’s the system.

Daily Commands

CommandWhen
/morningStart of day - surface priorities and open loops
/parkFinished working - save state and close cleanly
/pickupResuming work - pick up where you left off
/goodnightEnd of day - inventory and queue for tomorrow

Staying Current

The template gets regular updates - new commands, bug fixes, cross-platform improvements. To pull the latest:

/update

This updates commands and scripts only. Your CLAUDE.md and vault content are never touched. See Staying Current for details.

Tips

Plan Mode: Press Shift+Tab twice before asking Claude to do something. It’ll discuss its approach before making changes - good for learning how it thinks.

Don’t just ask for outputs. The real value is back-and-forth:

“Let’s brainstorm…” “What am I missing here?” “Can you ask me clarifying questions about…” “Let’s workshop this…”

The conversation is the thinking. Claude asking you questions and you refining your answers is often more valuable than the final document.

Everything compounds. Each file you create becomes context for future sessions. The more you put in, the smarter it gets about your business.