Claude Code Setup for Executive Coaches

# CLAUDE.md — Executive Coach
> Version: 2026-02-17 | Difficulty: beginner

## What Your AI Can Now Do
- Prepare a full client session brief — history, patterns, suggested questions — in 2 minutes instead of 30
- Generate quarterly sponsor progress reports that protect confidentiality while showing clear impact
- Spot recurring themes across all your clients so you coach the pattern, not just the symptom
- Draft accountability follow-ups that land with the right tone between sessions
- Build a searchable library of what works with which leader type over time

---

## Quick Start
1. Paste this file as `CLAUDE.md` in your coaching project root
2. Create your first client folder: `clients/[name]/session-notes/`
3. Run `/session-prep [client]` before your next call to see it in action
4. After the session, run `/session-notes` to capture commitments and insights
5. Add your coaching frameworks to `coaching-tools/frameworks/` so Claude can reference them

---

## About Me
Executive coach working with senior leaders (VP+) on leadership presence, strategic thinking, and organizational impact. Engagements run 6-12 months. The sponsor (usually their boss or HR) gets quarterly updates on themes and progress — never session details.

---

## Pre-Built Commands

| Command | What It Does |
|---------|-------------|
| `/session-prep [client]` | Builds a 1-page brief with recent session history, open commitments, emerging patterns, and 3 powerful questions |
| `/session-notes` | Captures session insights, commitments, and flags patterns — stores everything for next prep |
| `/progress-report [client]` | Generates a sponsor-safe quarterly summary: themes, growth areas, and impact — no session specifics |
| `/reflection` | Surfaces cross-client themes and coaching patterns you might be missing |
| `/intake [client]` | Creates new client folder with intake template, 360 feedback structure, and goal-setting framework |

---

## How Claude Connects to Your Tools

| Tool | Why You Need It |
|------|----------------|
| Google Workspace | Session scheduling, follow-up emails, progress report sharing with sponsors |
| AnySite (LinkedIn) | Research a client's public presence, org changes, or thought leadership before sessions |
| Memory | Tracks client goals, breakthroughs, blind spots, and commitments across every session |

### Setup
```bash
# Required in .env
GOOGLE_WORKSPACE_CREDENTIALS=your-credentials
MEMORY_STORAGE_PATH=./memory
```

---

## Coaching Rules
- **MUST:** Ask before telling — questions before advice, always
- **MUST:** Never break confidentiality — session content stays in session unless there is a safety risk
- **MUST:** Sponsor updates use themes and progress only — never specific session details or quotes
- **SHOULD:** Reflect back what you hear — "What I'm noticing is..." before offering a reframe
- **SHOULD:** Name the pattern, not the problem — clients see their own solutions when the pattern is visible
- **SHOULD:** End every session with: "What are you committing to before our next session?"
- **MUST:** Watch for dependency — if they cannot make decisions without you, you are advising, not coaching
- **SHOULD:** Celebrate progress explicitly — senior leaders rarely hear what is working

---

## Project Structure
```
clients/
  [client-name]/
    intake/              # Initial assessment, 360 feedback, goals
    session-notes/       # Dated notes from each session
    frameworks/          # Tools and models shared with this client
    progress-reports/    # Quarterly sponsor updates
coaching-tools/
  questions/             # Powerful question bank by topic
  frameworks/            # Leadership models, assessment tools
  exercises/             # Between-session assignments
memory/
  patterns/              # What approaches work for which leader types
  lessons/               # What you have learned as a coach
```

### What These Folders Mean
- **clients/** — One subfolder per client with all engagement artifacts. Claude reads this before every session prep.
- **coaching-tools/** — Your reusable toolkit. Questions, frameworks, and exercises Claude pulls from when building session plans.
- **memory/** — Long-term learning. Coaching patterns and lessons that improve suggestions over time.

---

## Automation

| When | What Happens | If It Fails |
|------|-------------|-------------|
| 30 min before session | Auto-runs `/session-prep` with full client context | Open the client folder manually and review last session notes |
| Session completed | Prompts for `/session-notes` capture | Write notes in `session-notes/` directly — do not skip this |
| Quarter end | Flags clients needing progress reports | Check `clients/*/progress-reports/` for last report date |
| 2 weeks since last session | Sends accountability check-in reminder | Review calendar manually for gaps in session cadence |
| New client intake | Creates folder structure and intake template | Run `/intake [client]` manually to scaffold the folder |

---

## Gotchas
- **MUST:** Document the commitment, not just the insight — insights without action items are expensive therapy
- **MUST:** Do not coach the problem, coach the person — the presenting issue is rarely the real issue
- **SHOULD:** If you feel drained after a session, check your boundaries — you may be holding something that belongs to the client
- **MUST:** Refer out when you see clinical issues — coaching is not therapy
- **SHOULD:** Track which powerful questions create the biggest shifts — your question library is your most valuable asset

---

## Memory & Learning
Claude builds context over time:
- Client goals, values, and what motivates each leader
- Commitments made and whether they followed through
- Recurring patterns and blind spots across sessions
- Which questions and frameworks resonated with each client
- Relationship dynamics mentioned (boss, peers, direct reports)

To save something important: just say "remember that [fact]" in conversation.
To review saved memories: use the `/memory` command to open the memory editor.