00 — START HERE: New Client Kit
This is the setup and orientation document for the New Client Kit. Read this to understand what it is, what it does, what files it needs, and how to use it.
What This Is
The New Client Kit scaffolds a fully functional client workspace repo from scratch. It takes a new client engagement and produces a complete directory structure, identity files (CLAUDE.md, WORKFLOW.md), settings, reference data, and README — everything needed to start running the weekly Advisory OS workflow.
This kit is structurally different from every other kit in the vault. Most kits produce a single document (a CPM, a master plan, a blueprint). This kit produces a directory structure — a whole repo scaffold with multiple files and folders. The output skill (05) contains embedded templates with placeholders.
Three Operating Modes
| Mode | Trigger | What It Produces |
|---|---|---|
| Mode 1: Day 0 Scaffold | New client signed | Repo structure, CLAUDE.md, WORKFLOW.md, README, .claude/settings.local.json, .gitignore, empty reference data, 9-step cascade skills in .claude/skills/, /start skill |
| Mode 2: Session 1 Population | First transcript available | Populated reference data, first CPM, master plan, project scaffolding |
| Mode 3: Maturity Upgrade | 3-5+ sessions, patterns emerge | Brand kit, client-specific skills, client-specific QC agents |
Mode 1 — Day 0 Scaffold
Run once when Kathryn signs a new client. Produces a fully functional workspace with the 9-step post-session cascade installed in .claude/skills/. The cascade auto-advances through all processing steps with human review gates between each. No client-specific production skills, brand files, or QC agents needed at this stage — the cascade references vault frameworks by default.
Prerequisite: GitHub repo already created. The kit documents the exact gh repo create command but does not execute it.
Mode 2 — Session 1 Population
Run after the first session transcript is available. Populates reference data from the transcript, produces the first CPM (using the vault CPM framework), creates the master plan, and scaffolds the first project if an initiative is identified.
This mode calls other vault frameworks. The kit coordinates — it doesn't duplicate CPM, master plan, or project plan logic.
Mode 3 — Maturity Upgrade
Not a single operation. Each upgrade is independent and happens over weeks or months as patterns emerge:
- Brand kit (3 files: HTML reference + brand skill + brand QC) — when brand patterns are clear (typically session 3-5+)
- Client-specific skills — when recurring document types need client-customized production rules
- Client-specific QC agents — when quality patterns specific to this client emerge
Mode 3 actions are incremental. "Create brand kit" is a separate action from "create SOP skill." Each one updates CLAUDE.md and WORKFLOW.md to reference the new file.
What This Does NOT Do
- Does not create the GitHub repo (manual prerequisite —
gh repo create) - Does not produce deliverables (CPMs, master plans, blueprints — those are separate frameworks)
- Does not configure Relay (that's a separate platform setup)
- Does not set up Google Drive sync (documented in two-machine workflow, not automated)
- Does not create the engagement contract or pricing (business decision, not a kit operation)
Gold Standard References
| Repo | Status | Role |
|---|---|---|
aos-client-jb (Jenn Barr / TRG Consultants) | Latest tested | 9-step post-session cascade (tested and working), full .claude/skills/ setup. The reference for cascade skill structure. |
aos-client-rc (Ruben Cruz / Crulliance) | Fully mature | 9-step cascade + brand kit (3 files), 8 production skills in skills/, 2 QC agents. The gold standard for a fully built-out workspace with client-specific customization. |
Both repos use the same 9-step post-session cascade in .claude/skills/, identical directory structures, and the same weekly workflow. RC's cascade skills reference client-specific production skills and brand files; JB's cascade skills are self-contained.
File Inventory
| # | File | What It Is |
|---|---|---|
| 00 | 00-new-client-kit-start-here.md | This file — orientation, modes, what it does and doesn't do |
| 01 | 01-new-client-kit-context.md | Required inputs per mode, validation rules |
| 02 | 02-new-client-kit-terminology.md | Locked vocabulary for this kit |
| 03 | 03-new-client-kit-golden-example.md | Structural reference pointing to both live repos with annotations |
| 04 | 04-new-client-kit-quality.md | Four checklists — Mode 1 gate (24 items), Mode 2 gate, readiness checklist, Mode 3 gate |
| 05 | 05-new-client-kit-output-skill.md | The production skill — templates, step-by-step scaffold instructions |
Total: 6 files.
Relationship to Other Kits
This kit is the entry point for the client engagement workflow. It runs before any other framework kit:
New Client Kit (Mode 1) → Day 0 scaffold + 9-step cascade skills
↓
New Client Kit (Mode 2) → Calls CPM framework, Master Plan framework
↓
Weekly workflow begins (9-step cascade in .claude/skills/)
↓
New Client Kit (Mode 3) → Brand kit, client-specific production skills, QC agents
(cascade skills updated to reference them)The kit coordinates with but does not duplicate:
- Constraint Priority Matrix (
content/frameworks/kit-constraint-priority-matrix/) — called during Mode 2 - Master Plan (
content/frameworks/kit-master-plan/) — called during Mode 2 - Reference Data (
content/frameworks/kit-reference-data/) — template copied during Mode 1, populated during Mode 2 - Deployment Cycle (
content/frameworks/kit-deployment-cycle/) — referenced in WORKFLOW.md, used during builds - Project Plan (
content/frameworks/kit-project-plan/) — called when initiative is scoped - Blueprint (
content/frameworks/kit-blueprint/) — called when initiative is scoped
File Location
advisory-os-vault/content/frameworks/kit-new-client/
00-new-client-kit-start-here.md (this file)
01-new-client-kit-context.md
02-new-client-kit-terminology.md
03-new-client-kit-golden-example.md
04-new-client-kit-quality.md
05-new-client-kit-output-skill.md