1:1 Recap Kit — Start Here
What This Kit Does
Produces a recap email and a full personal-notes document after a paid 1:1 session that isn't an AOS DFY engagement and isn't a TPC mastermind group call.
Use cases:
- TPC mastermind member 1:1s (Rob, Tracy, Meryl, etc.)
- Post-tax-season debrief 1:1s
- Ad-hoc paid advisory 1:1s
- Stakeholder 1:1s for engagements that don't have a full project plan / cascade
Not for:
- AOS DFY clients (Ruben, Jenn) — the 10-step cascade in their client repos owns those
- TPC Momentum Monday group calls —
kit-tpc-post-momentum-monday/owns those - Free / peer / one-off non-client meetings —
business-aos/.claude/skills/recap-meeting.mdowns those
Outputs (the full cascade)
| # | Output | Vehicle | Audience | Where |
|---|---|---|---|---|
| 1 | Recap email | Gmail draft (created via API) | Client | Gmail draft folder |
| 2 | Full personal recap | Markdown | Kathryn | cyp/tpc/members/[name]/sessions/[firstname]-1on1-[YYYY-MM-DD].md |
| 3 | Prep email for next session | Gmail draft | Client | Gmail draft folder (sends 2 business days before next session) |
| 4 | Calendar events | Google Calendar | Kathryn | Prep + agenda events for the next session |
| 5 | Member mini-CPM | Markdown | Kathryn | cyp/tpc/members/[name]/cpm/[name]-cpm-[YYYY-MM-DD].md |
| 6 | Drafted deliverables (action items) | Markdown — one per item | Kathryn | cyp/tpc/members/[name]/drafts/[slug]-[YYYY-MM-DD].md |
| 7 | Action-items index (navigation) | Markdown | Kathryn | cyp/tpc/members/[name]/sessions/[name]-action-items-[YYYY-MM-DD].md |
| 8 | Updated open-actions running list | Markdown (in place) | Kathryn | cyp/tpc/members/[name]/open-actions.md |
| 9 | Lessons for Practice Builders OS — General | Markdown (new or appended) | Kathryn / future PBOS-General design | cyp/tpc/lessons-learned/[topic].md |
| 10 | Cascade report — pre-send review | Markdown + Gmail draft to Kathryn | Kathryn | cyp/tpc/members/[name]/sessions/[name]-cascade-report-[YYYY-MM-DD].md + inbox |
Operating Modes
| Mode | Trigger | What It Produces |
|---|---|---|
| Mode 1: Full Run | Transcript available after a paid 1:1 | All 10 outputs above, in sequence, auto-advancing |
| Mode 2: Improve | Manual edits to a sent email, QC missed something, kit needs updating | Updated kit files |
File Inventory
| # | File | Purpose |
|---|---|---|
| 00 | 00-1on1-recap-start-here.md | This file |
| 01 | 01-1on1-recap-context.md | Inputs, validation, content filter |
| 02 | 02-1on1-recap-terminology.md | Locked vocabulary, forbidden terms |
| 03 | 03-1on1-recap-golden-example.md | Rob 3-11-2026 reference email |
| 04 | 04-1on1-recap-quality.md | QC checklist (pass/fail) for recap email |
| 05 | 05-1on1-recap-output-skill.md | Production workflow — recap email + .md + prep email + calendar (Steps 1-14, includes Step 5 Ledger as the structural protection) |
| 06 | 06-1on1-recap-update-member-cpm.md | Per-member mini-CPM update |
| 07 | 07-1on1-recap-draft-actions.md | Detect signals → route to the member rollup + Pipeline board (Phase 1 Build C); + send-wrapper for existing shared assets. No longer drafts Kathryn deliverables/builds for the member — banned by the file 01 stance. |
| 08 | 08-1on1-recap-update-open-actions.md | Update the running open-actions list per member |
| 09 | 09-1on1-recap-extract-lessons-learned.md | Route IP to lessons-learned for Practice Builders OS — General |
| 10 | 10-1on1-recap-cascade-report.md | Pre-send review — final Kathryn-facing report, GREEN/YELLOW/RED status |
Total: 11 files. Auto-advancing cascade.
Triage first — match the effort to the call
Not every 1:1 earns the full cascade. A thin/cut-short/no-decision call gets a short note + a one-line board touch, then stop (file 05 Step 0.5). The full chain below runs only for substantive sessions — ones that produced decisions, commitments, builds, or action items. Running the machinery on a thin call costs Kathryn more time than writing the note herself; that's the failure mode, not a thoroughness virtue. The standing test: an output that costs more to fix than to write has failed.
The Cascade Chain
/recap-1on1 (file 05 — recap email + .md + prep email + calendar) ↓ /update-member-cpm (file 06) ↓ /draft-1on1-actions (file 07) ↓ /update-open-actions (file 08) ↓ /extract-lessons-learned (file 09) ↓ /cascade-report-1on1 (file 10) — final, presents pre-send status to Kathryn
Each step auto-advances. Cascade-report is the safety net: surfaces what needs Kathryn's eyes before any client-facing artifact (recap email, prep email) ships.
Relationship to Other Kits
| Kit / Skill | Relationship |
|---|---|
AOS DFY cascade (aos-client-*/.claude/skills/recap-email) | Sister system. 10-step cascade with project-plan / CPM / blueprint integration. This kit is the right-sized alternative when no cascade machinery applies. |
TPC Momentum Monday (kit-tpc-post-momentum-monday/) | Sister kit. Same advisor, group format. This kit handles the 1:1s with TPC members between Monday calls. |
Generic non-client (business-aos/.claude/skills/recap-meeting.md) | Predecessor pattern for free/peer meetings. Lighter, no client-recap discipline. |
The Rule That Makes This Kit Work
Extract first. Compose second.
This kit treats writing as two phases. Steps 1–5 of file 05 produce structured artifacts (transcript notes, calendar facts, the Commitments / Decisions / Specifics Ledger). Steps 6–8 compose prose that draws only from those artifacts. Every sentence in the email must trace to a ledger row or a reference data value — never to model judgment at the sentence level.
The Rob 3-11-2026 email (file 03) is the structural standard for the output: opener → wins → what we covered (one line each) → action items (by owner) → proposed agenda → warm close. Five sections, no bloat. The ledger is the structural standard for the input — what's extracted, classified, and traceable before any prose gets written.
When errors surface in QC (file 04, Gate 2): the fix is upstream, not in the prose. A missing ledger row, a stale reference data entry, a wrong cadence vocabulary lookup. File 04 is a traceability gate, not a graders' rubric.