Source: frameworks/kit-new-client/04-new-client-kit-quality.md
04 — QUALITY: New Client Kit
Four checklists — one per mode gate, plus a readiness checklist for weekly operations.
Mode 1 Gate — Day 0 Scaffold Complete (28 items)
Run this checklist after completing Mode 1. All 24 items must pass before the workspace is considered scaffolded.
Repo Structure (12 items)
| # | Check | Pass/Fail |
|---|
| 1 | sessions/ directory exists | |
| 2 | inputs/ directory exists | |
| 3 | drafts/ directory exists | |
| 4 | ready/ directory exists | |
| 5 | archive/ directory exists | |
| 6 | constraints/ directory exists | |
| 7 | master-plan/ directory exists | |
| 8 | projects/non-project-specific/ directory exists | |
| 9 | reference/core/ directory exists | |
| 10 | reference-data/ directory exists | |
| 11 | kits/ and frameworks/ directories exist (empty is correct) | |
| 12 | brand/, skills/, and qc-agents/ directories exist (empty is correct) | |
Identity Files (8 items)
| # | Check | Pass/Fail |
|---|
| 13 | CLAUDE.md exists at repo root | |
| 14 | CLAUDE.md header contains: client name, company, engagement type, rate, cadence, start date | |
| 15 | CLAUDE.md has Session Opener section with kanban flow | |
| 16 | CLAUDE.md has Weekly Workflow table with Steps 0-6 | |
| 17 | CLAUDE.md has Where Things Are table with correct file paths (includes sessions, inputs, drafts, ready, archive, reference/core) | |
| 18 | CLAUDE.md has Connected Repos section (vault + business-aos) | |
| 19 | CLAUDE.md has Rules section with client name substituted | |
| 20 | WORKFLOW.md exists at repo root with Email QC, Steps 1-6 each having STOP — Human Review, reference data first rule, background agent rule | |
Reference Data (3 items)
| # | Check | Pass/Fail |
|---|
| 21 | reference-data/{{preferred-name}}-reference-data.md exists | |
| 22 | Reference data has correct client name and company in header | |
| 23 | Reference data Engagement section has entry point, rate, cadence, start date, advisor pre-filled | |
Cascade Skills (4 items)
| # | Check | Pass/Fail |
|---|
| 24 | .claude/skills/start/SKILL.md exists with correct client name, repo path, reference data path | |
| 25 | All 9 cascade skill directories exist in .claude/skills/: recap-email, recap-internal, recap-json, update-cpm, update-masterplan, update-projectplan, update-blueprint, draft-actions, session-agenda | |
| 26 | Each cascade SKILL.md has correct client name, file paths, reference data path, and auto-advance instruction pointing to next step | |
| 27 | Final cascade step (session-agenda) reports "Cascade complete. All 9 steps finished." | |
Settings & Additional Files (1 item)
| # | Check | Pass/Fail |
|---|
| 28 | .claude/settings.local.json exists with correct additionalDirectories (advisory-os-vault + business-aos, both Windows and Linux paths), .gitignore exists, README.md exists with client info and folder structure | |
Pass threshold: 28/28. Every item is required.
Mode 2 Gate — Session 1 Population Complete (9 items)
Run this checklist after completing Mode 2.
| # | Check | Pass/Fail |
|---|
| 1 | Reference data populated — team roster has at least the client, tools section has known tools, proper nouns corrected | |
| 2 | Reference data update log has an entry for initial population | |
| 3 | First CPM produced — constraints/{{preferred-name}}-constraint-priority-matrix-YYYY-MM-DD.md exists | |
| 4 | CPM passes vault quality checklist (04 file) with score 90+ | |
| 5 | CPM has been reviewed and approved by Kathryn | |
| 6 | Master plan created — master-plan/client-master-plan-{{full-name}}.html exists | |
| 7 | Master plan passes vault QC (06 file) | |
| 8 | If initiative identified: project directory scaffolded under projects/ with standard subdirectories (blueprint, project-plan, builds, deployment, drafts, inputs, outputs) | |
| 9 | CLAUDE.md updated — Active Projects section reflects any scaffolded projects, Where Things Are table updated with project paths | |
Pass threshold: All applicable items. Item 8 is conditional on an initiative being identified.
Readiness Checklist — "Ready for Weekly Operations" (12 items)
This is the comprehensive gate between "workspace exists" and "weekly workflow starts running." Run this before the first regular processing session.
Infrastructure (4 items)
| # | Check | Pass/Fail |
|---|
| 1 | GitHub repo accessible — git pull works from both machines | |
| 2 | .claude/settings.local.json working — Claude can read vault and business-aos files | |
| 3 | Google Drive sync documented — Kathryn knows where transcripts land and how to move them to inputs/ | |
| 4 | Relay configured — session transcripts produce JSON analysis files automatically | |
Documents (4 items)
| # | Check | Pass/Fail |
|---|
| 5 | CLAUDE.md accurately reflects current engagement (name, rate, cadence, projects) | |
| 6 | WORKFLOW.md reflects actual schedule (session days, processing days, cadence) | |
| 7 | Reference data verified — at minimum: client name, company, team roster, known tools | |
| 8 | Master plan exists with at least one processed session | |
Process (3 items)
| # | Check | Pass/Fail |
|---|
| 9 | Claude responds correctly to /recap-email — reads transcript, produces Gmail draft, auto-advances through all 9 cascade steps with human review gates | |
| 10 | All 9 cascade steps produce output — recap email, internal recap, profile JSON, CPM, master plan update, project plan update (if project exists), blueprint update (if project exists), draft actions, session agenda + advisory email | |
| 11 | Human review gates are clear — Claude stops after each step, Kathryn knows where to look and what to approve | |
Client-Side (1 item)
| # | Check | Pass/Fail |
|---|
| 12 | Transcript export tested — at least one session has been transcribed, exported, and processed end-to-end | |
Pass threshold: 12/12. All items required. Items 10's project plan/blueprint/builds steps are conditional on a project existing.
Mode 3 Gate — Maturity Upgrade Complete (9 items)
Run the applicable section each time a Mode 3 action is completed. These are independent — you don't need to complete all three categories at once.
Brand Kit Created (3 items)
| # | Check | Pass/Fail |
|---|
| 1 | Brand skill exists in brand/ — covers colors, typography, terminology, document-specific rules | |
| 2 | Brand QC exists in brand/ — quality gate for brand compliance, layers on vault copy QC | |
| 3 | CLAUDE.md and WORKFLOW.md updated to reference brand files (brand skill listed as prerequisite for client-facing docs) | |
Client-Specific Skill Created (3 items)
| # | Check | Pass/Fail |
|---|
| 4 | Skill file exists in skills/ with naming pattern {{brand-name}}-{{doc-type}}-skill.md | |
| 5 | Skill references the vault framework it extends (not duplicating framework logic) | |
| 6 | CLAUDE.md Skills Quick Reference table updated, WORKFLOW.md step references updated | |
Client-Specific QC Created (3 items)
| # | Check | Pass/Fail |
|---|
| 7 | QC file exists in qc-agents/ with naming pattern {{brand-name}}-{{doc-type}}-qc.md | |
| 8 | QC layers on vault QC (adds client-specific checks, doesn't replace vault checks) | |
| 9 | CLAUDE.md QC Quick Reference table updated, WORKFLOW.md quality gate references updated | |
Pass threshold: All items in the applicable section. Each section is independent.