00 — START HERE: TPC Post-Momentum-Monday Kit
Setup and orientation for processing a TPC Momentum Monday call into the full set of artifacts the engagement requires.
What This Is
The TPC post-Momentum-Monday kit takes a single Momentum Monday transcript and produces eight artifacts. It exists because TPC is a facilitated mastermind, not a generic peer meeting — the post-session work is part of the facilitation, not a recap-after-the-fact. Generic /recap-meeting doesn't do what TPC needs. The 1:1 advisory kit-post-session-production doesn't either.
Audience:
- Member-facing artifacts: TPC group members
- Facilitator-facing artifacts: Kathryn only
Format: Mix — markdown, HTML (Gmail-paste), JSON. See file inventory in 05.
Lifecycle: One run per Momentum Monday. Repeats weekly during cohort active season.
Outputs
| # | Output | Audience | Format | Where |
|---|---|---|---|---|
| 1 | Monday group recap email (newsletter, MailerLite) | TPC members | Markdown source + HTML | cyp/tpc/drafts/tpc-monday-recap-[YYYY-MM-DD].md + .html |
| 2 | Personal facilitator recap | Kathryn | Markdown | cyp/tpc/sessions/tpc-momentum-monday-[YYYY-MM-DD].md |
| 3 | Facilitator review (your-eyes-only) | Kathryn | Markdown | cyp/tpc/sessions/tpc-momentum-monday-[YYYY-MM-DD]-facilitator-review.md |
| 4 | Member-file updates | Kathryn | Append to existing | cyp/tpc/members/[member].md (each attendee + light note for absentees) |
| 5 | JSON | Kathryn (machine-readable) | JSON | cyp/tpc/sessions/tpc-momentum-monday-[YYYY-MM-DD].json |
| 6 | Planning doc update | Kathryn | Append to planning doc | cyp/tpc/planning/tpc-communication-arc-through-mastermind.md |
| 7 | Lessons-learned entry (if applicable) | Kathryn / Practice Builders | Markdown | cyp/tpc/lessons-learned/lesson-[topic]-[YYYY-MM-DD].md |
| 8 | Friday email skeleton | Kathryn (template) | Markdown | cyp/tpc/drafts/tpc-friday-email-[YYYY-MM-DD]-skeleton.md |
| 9 | Google Doc overview entry (the depth-version of the email — paste into 2026: TPC Group Session Chat Google Doc) | TPC members (via the linked doc) | Markdown for paste | cyp/tpc/drafts/tpc-doc-overview-[YYYY-MM-DD].md |
| 10 | Kathryn's Action Items — build/listen items, decision items, doc-update items, with calendar events proposed for deep-work blocks and Gmail drafts created only when warranted | Kathryn | Markdown + Gmail drafts (as needed) + calendar events (as needed) | cyp/tpc/sessions/tpc-action-items-[YYYY-MM-DD].md |
| 10b | Listen-pass extraction template — workspace Kathryn fills during the Friday-into-weekend listen-pass on member recordings. Recording inventory, per-member raw notes, cross-cutting patterns, comparison against most-recent-Monday patterns, confidentiality flags, scaffold implications, decision-item resolutions | Kathryn | Markdown | cyp/tpc/group/otter-pattern-extraction-[YYYY-MM-DD].md (date = recording deadline, typically the Friday) |
| 11 | Next Monday's facilitation guide — produced from the listen-pass extraction (10b) PLUS the most-recent personal recap + facilitator review. The bridge from "what came in over the week" to "how the room runs next Monday." Pulls patterns extracted in 10b directly into the session flow. | Kathryn | Markdown | cyp/tpc/drafts/tpc-monday-facilitation-guide-[YYYY-MM-DD].md (date = next Monday) |
About Outputs 1 + 9 (the email-and-doc pair):
The Monday recap email is the digest. The Google Doc overview is the depth. The email's two consistent links — recording and chat — point to (a) the Zoom recording folder and (b) the Google Doc. The email summarizes; the doc gives the full member-by-member breakdown with quotes inline and the chat log.
Same content, two depths, one delivery system.
Operating Modes
| Mode | Trigger | What It Produces |
|---|---|---|
| Mode 1: Full Run | Transcript available after a Momentum Monday | All twelve outputs (1–10 produced same day; 10b template populated through the week; 11 produced Sunday before next Monday) |
| Mode 2: Improve | Manual changes to outputs, QC missed something, kit needs updating | Updated kit files |
Mode 1 — Full Run
The standard run. Inputs: Monday transcript, prior member files, prior session artifacts, facilitation guide for the session, planning doc current state. Outputs: all eight artifacts above.
Mode 2 — Improve This Kit
Self-improvement loop. After running the kit:
- Did Kathryn change anything in any output by hand? → Update the relevant golden example reference + output skill
- Did QC miss something Kathryn caught? → Update the quality checklist
- Should the kit produce something it didn't? → Update the output skill or add a new output
What This Does NOT Do
- Does not send emails. Drafts only. Kathryn sends.
- Does not commit or push files. Kathryn (or
/end) handles git. - Does not update the facilitation guide for the next session — that's a separate skill (
session-agendaor equivalent). - Does not produce calendar events. Calendar work happens in a follow-on workflow.
- Does not generalize to non-TPC group meetings. That's a future kit (
kit-post-group-session-production— generalized).
File Inventory
| # | File | What It Is |
|---|---|---|
| 00 | 00-tpc-post-momentum-monday-start-here.md | This file — orientation, outputs, modes |
| 01 | 01-tpc-post-momentum-monday-context.md | Required inputs, validation rules, input priority |
| 02 | 02-tpc-post-momentum-monday-terminology.md | Locked vocabulary — TPC-specific terms |
| 03 | 03-tpc-post-momentum-monday-golden-example.md | Structural reference pointing to the 2026-04-27 run |
| 04 | 04-tpc-post-momentum-monday-quality.md | QC checklist — per-output + cross-output |
| 05 | 05-tpc-post-momentum-monday-output-skill.md | The production skill — overview + per-output requirements |
| 06 | 06-tpc-post-momentum-monday-instructions.md | Step-by-step procedures for each of the eight outputs |
| 07 | 07-tpc-post-momentum-monday-facilitator-review.md | Facilitator-review methodology — comparing to the facilitation guide, naming the deviations |
Total: 8 files (extended kit). Justified: 8 distinct output procedures bloat the output skill if combined; facilitator-review is methodology-heavy enough to warrant its own file.
Confirm Understanding Before Executing
Before any production run, confirm with Kathryn:
"I have the [date] transcript and the [date] facilitation guide. I'm going to produce all eight outputs in this order: Monday recap email, personal recap, facilitator review, member updates, JSON, planning doc append, lessons-learned (if applicable), Friday skeleton. Does that match your intent?"
Do not start production until Kathryn confirms.
Relationship to Other Kits
| Kit | Relationship |
|---|---|
| kit-post-session-production (1:1 advisory) | Sister kit. Different audience (group vs. 1:1). Different cadence (Monday same-day vs. post-session-with-friction-analysis). Same rigor on transcript-as-source. |
| recap-meeting (generic non-client) | Predecessor pattern. Produces 3 outputs (group email + personal recap + JSON). This kit extends with 5 additional outputs specific to facilitated cohorts. |
| kit-builder | This kit was built from kit-builder Mode 1 using the 2026-04-27 run as the golden example set. Future improvements via Mode 2. |
File Location
advisory-os-vault/content/frameworks/kit-tpc-post-momentum-monday/
00-tpc-post-momentum-monday-start-here.md (this file)
01-tpc-post-momentum-monday-context.md
02-tpc-post-momentum-monday-terminology.md
03-tpc-post-momentum-monday-golden-example.md
04-tpc-post-momentum-monday-quality.md
05-tpc-post-momentum-monday-output-skill.md
06-tpc-post-momentum-monday-instructions.md
07-tpc-post-momentum-monday-facilitator-review.md