← Vault Index
frameworks / kit-tpc-post-momentum-monday / 06-tpc-post-momentum-monday-instructions.md
Source: frameworks/kit-tpc-post-momentum-monday/06-tpc-post-momentum-monday-instructions.md

06 — INSTRUCTIONS: TPC Post-Momentum-Monday Kit

Step-by-step procedures for each of the eight outputs. File 05 gives the orchestration; this file gives the per-output execution detail.

Phase 1 — Read (no writing yet)

1.1 Read all 7 member files

Open cyp/tpc/members/ and read every file:

Note for each: current engagement profile, prior watch-fors, current threads, prior session contributions if any.

1.2 Read TPC CLAUDE.md

cyp/tpc/CLAUDE.md. Confirm: cohort roster, cadence, routing rules, current 3-event arc.

1.3 Read facilitation guide for the session

cyp/tpc/drafts/tpc-monday-facilitation-guide-YYYY-MM-DD.md. Note: planned session flow, planned watch-fors, capture sheet structure, "what success looks like" criteria.

1.4 Read planning doc current state

cyp/tpc/planning/tpc-communication-arc-through-mastermind.md. Note: current arc, recent updates, threads-to-revisit.

1.5 Read transcript end-to-end

cyp/tpc/sessions/[transcript filename].txt. Read fully. Looking for:

1.6 Identify attendees + absentees

Cross-check transcript speaker list against TPC roster. Anyone in roster who didn't speak = absent. Categorize each absentee:

1.7 Run Gate 1 (file 04) — pre-build readiness

If any check fails, stop. Get the missing input or confirm with Kathryn how to proceed.

1.8 Confirm with Kathryn

Use the language from file 00:

"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?"

Wait for confirmation.

Phase 2 — Extract

2.1 Member-by-member contribution extraction

For each attendee, build a working list:

2.2 Quote harvest

Pull every quote that's worth keeping. For each: speaker (canonical spelling), context (why it matters), original transcript location.

Criteria for keeping a quote:

2.3 Action items — three buckets

2.4 Plan-vs-actual analysis

Compare facilitation guide to transcript section-by-section:

2.5 Lessons-learned trigger check

Ask: did Kathryn (or the session) reveal something she'd do differently next time? Indicators:

If yes → produce output 7. If no → skip output 7.

Phase 3 — Produce

3.0 Output 9 — Google Doc overview entry (produce FIRST)

Why first: Output 9 is the fuller (but still thin) companion; Output 1 (email) summarizes from it. Produce the doc overview first, then the tighter email digest.

Step 1. Open cyp/tpc/drafts/tpc-doc-overview-2026-06-08.md (the thin golden, recalibrated 6-8-2026) for format reference. Study: how few topics, how light the sub-bullets, and fixes framed as "made native for you" — not snags. (The older 2026-05-04 version is too expansive; don't mirror its depth.)

Step 2. Draft. Structure:

#### **Momentum Monday: M-DD-YYYY**

**What We Discussed**

1.  [Topic title — short, factual]

      - [Sub-bullet: what happened, who said what]
      - [Member: "quote" — context if needed]
      - [Sub-bullet]

2.  [Next topic]
      - ...

Step 3. Apply the Output 9 rules from file 05:

Step 4. Length check: keep it THIN — ~3-4 tight topics, a handful of sub-bullets each (recalibrated 6-8-2026). If you're past 4 topics or restating the whole session, cut. For a hands-on/working session, even less.

Step 5. Save to cyp/tpc/drafts/tpc-doc-overview-YYYY-MM-DD.md.

3.1 Output 1 — Monday recap email

Step 1. Open cyp/tpc/drafts/tpc-monday-recap-2026-06-08.md (the as-sent golden) for voice + structure; the most recent Friday email in archive/ for tonal match.

Step 2. Draft markdown source. Structure (recalibrated 6-8-2026):

# TPC Monday Recap — YYYY-MM-DD

**Audience:** TPC group (MailerLite group "Offer | The Tax Pro Collaborative")
**Sent:** Monday M-DD via MailerLite
**Format:** Markdown source. HTML in this folder for Gmail-paste fallback.

---

## Subject

TPC: Momentum Monday Recap- M-DD-YYYY

---

## Body

Hi there,

[Optional warm opener — one short line, e.g. "Welcome to June!"]

Here's your recap from this week's Momentum Monday.

If you want to hear the conversation, [here's the link](RECORDING). If you'd like to see the session notes, [here's the link](DOC).

**What we covered:** [ONE–2 sentences — the session arc]

**Highlights:**
- [ONE framing bullet — what the session was, at altitude. NOT a tactical/teaching list.]

**What Surfaced**
- **[Present member]:** [one line of substance; brief acknowledgment of a significant life moment if any]
[one line per present member]
- **[Absent members, combined]:** Missed you — [walk-through coming + offer of co-working/1:1 help. NOT "watch the recording."]

**Housekeeping:** [Co-working framed as "bring what you're stuck on" + Calendly. Tight. Don't promise depth or telegraph going deeper.]

Talk soon,
Kathryn

Step 3. Convert to HTML. Inline styles only. Use —, &, – correctly. No scripts, no external stylesheets.

Step 4. Save both files to cyp/tpc/drafts/ with tpc-monday-recap-YYYY-MM-DD.md + .html.

3.2 Output 2 — Personal facilitator recap

Step 1. Open cyp/tpc/sessions/tpc-momentum-monday-2026-04-13.md for format reference.

Step 2. Draft. Structure (mirroring 4-13 + 4-27 formats):

# TPC Momentum Monday — Personal Recap
**Date:** [Month DD, YYYY]
**Meeting:** Tax Pro Collaborative — Momentum Monday
**Attendees:** [list]
**Absent:** [list with reasons]

## Summary
[2-4 sentences capturing session arc + any deviation]

## What We Discussed (in order)
[Numbered sections in transcript order. Each major topic gets a section.
For member-led contributions: name the member and give specific detail.]

## My Takeaways
[Bullet-level. Each takeaway connects to Kathryn's broader work / IP / clients.]

## Connections to Follow Up
| Person | What they said | Follow-up |
[One row per attendee + absentees]

## Action Items
[- [ ] checkbox list]

## Ideas Sparked
[Numbered list — each idea links to part of Kathryn's business]

## Quotes Worth Remembering
[Block quotes with speaker + context]

Step 3. Save to cyp/tpc/sessions/tpc-momentum-monday-YYYY-MM-DD.md.

3.3 Output 3 — Facilitator review

Step 1. Open cyp/tpc/sessions/tpc-momentum-monday-2026-04-27-facilitator-review.md for format reference.

Step 2. Draft. Required sections:

# TPC Momentum Monday — Facilitator Review
**Date:** [date]
**Audience:** Your eyes only.

[Brief intro line about what this is]

## Did the session do its job?
[Compare to facilitation guide's "what success looks like" criteria.
Honest read. Net assessment.]

## Where you held the plan
[Bullet what you did per the guide]

## Where you broke from the plan
[For each departure: What happened, Cost, Benefit, Honest question.]

## Airtime and dominance patterns
[Rough estimates by member. Watch-fors that fired or didn't.]

## What landed in the room
[Frames, moves, moments that worked]

## What didn't land
[Things to fix or pre-empt]

## Single biggest indicator the session worked
[Per the guide's metric — did it work? Specifics.]

## Calibration for next [session date]
[Numbered list of specific actions]

## What this session is teaching about TPC as a live lab
[Pattern-level — what's the broader learning]

Step 3. Save to cyp/tpc/sessions/tpc-momentum-monday-YYYY-MM-DD-facilitator-review.md.

3.4 Output 4 — Member file updates

For each attendee:

Step 1. Read current member file.

Step 2. Decide: append-only or revise-existing?

Step 3. Append section structure:

---

## YYYY-MM-DD Session Contributions

**[Topic, e.g., AI use cases shared]:**
- [Specific contribution]
- [Specific contribution]

**[Pain points named for X]:**
- [Pain]

**Quote for the file:** *"[exact quote]"* (on [context])

**Commitment:** [What they committed to and the deadline]

**Watch-for added:** [New facilitation watch-for]

For each absentee:

---

## YYYY-MM-DD Session Note

**Absent. [Reason or "No notice."]** [Brief context about what happened in the session.]

**Action:** [Specific reach-out or wait-for-signal action]

**[Optional:] If they send a recording / when they return:** [Forward-looking watch-for]

Step 4. Save each member file.

3.5 Output 5 — JSON

Step 1. Open cyp/tpc/sessions/tpc-momentum-monday-2026-04-27.json for the extended schema reference.

Step 2. Build JSON matching that schema:

{
  "meetingDate": "YYYY-MM-DD",
  "meetingType": "Tax Pro Collaborative — Momentum Monday",
  "participants": ["Kathryn Brown", ...],
  "absent": [{"name": "X", "reason": "Y"}],
  "conversation": {"summary": "...", "keyTopics": ["..."]},
  "takeaways": [{"insight": "...", "relevanceTo": "...", "actionable": true|false}],
  "actions": [{"task": "...", "source": "...", "due": "YYYY-MM-DD or empty"}],
  "quotes": [{"text": "...", "speaker": "...", "context": "..."}],
  "connections": [{"person": "...", "topic": "...", "followUp": "..."}],
  "ideas": [{"idea": "...", "linkedTo": "..."}]
}

Step 3. Validate parseable JSON.

Step 4. Save to cyp/tpc/sessions/tpc-momentum-monday-YYYY-MM-DD.json.

3.6 Output 6 — Planning doc append

Step 1. Read current planning doc end.

Step 2. Decide: arc shifted, arc holds, arc adjusted?

Step 3. Append a new section at the bottom:

---

## YYYY-MM-DD Update — Arc [Has Shifted | Holds | Adjusted]

[1-paragraph description of what changed and why]

[If shifted: revised arc table]

**What's new in the arc:**
[Numbered or bullet list]

**What's still uncertain:**
[Bullet list]

**Facilitator-review insight:** [Cross-reference to facilitator review]

Step 4. Save the planning doc.

3.7 Output 7 — Lessons-learned entry (conditional)

Decision gate: Was a real lesson surfaced? (See 2.5 above.)

If no: Skip. Note in Mode 2 wrap-up: "Lessons-learned skipped this run — no lesson surfaced."

If yes:

Step 1. Read cyp/tpc/lessons-learned/README.md for format.

Step 2. Draft using that format. One file per lesson.

Step 3. Save to cyp/tpc/lessons-learned/lesson-[topic-slug]-YYYY-MM-DD.md.

3.8 Output 8 — Friday email skeleton

Step 1. Open cyp/tpc/drafts/tpc-friday-email-2026-05-01-skeleton.md for format reference.

Step 2. Identify the job-of-the-week:

Step 3. Draft the skeleton:

# TPC Friday Email — YYYY-MM-DD (Skeleton)

**Audience:** [list]
**Send:** Friday M-DD, late afternoon
**Job (one job, not five):** [The single job]

---

## Job-of-the-week
[1-paragraph context for what this email needs to do]

## Subject line options
[3 options]

## Skeleton
[Section-by-section template with placeholder text]

## What to verify before sending
[Numbered checklist]

## Why each section is there
[Per-section rationale]

## Do NOT
[Failure-mode list]

Step 4. Save to cyp/tpc/drafts/tpc-friday-email-YYYY-MM-DD-skeleton.md.

Step 5. Add to top of skeleton (mandatory header):

Voice rule for filling this skeleton: The example text in [brackets] is structural reference only — what kind of beat goes there. Do NOT paraphrase or polish it. When filling, voice anchors are (a) the most recent shipped Friday email in archive/ and (b) the most recent transcript in cyp/tpc/transcripts/. See file 05 Voice Anchor Rule.

3.9 Output 10b — Listen-pass extraction template

Step 1. Open cyp/tpc/group/otter-pattern-extraction-2026-05-01.md for format reference (the 5-1 baseline).

Step 2. Build the template at cyp/tpc/group/otter-pattern-extraction-[next-Friday-date].md:

# Otter Recording Pattern Extraction — YYYY-MM-DD

**Listen-pass for:** [what the recordings are about, from action items doc]
**Purpose:** Pull patterns across recordings to feed the next Monday facilitation guide and any weekend build block.
**Cross-references:** [pointers to: this Monday's personal recap, facilitator review, action items doc, Friday email]

---

## Recording Inventory

| Member | Received? | Length | File location | Notes |
|---|---|---|---|---|
[7 rows — full TPC roster with relevant flags (medical leave, absent-no-notice, etc.)]

**Engagement read by counts:**
- Sent by EOD [Friday]: ___ of 7
- Of the [N] in-room on this Monday: ___
- Of the absent-no-notice members: ___
- Late arrivals: ___

---

## Per-Recording Raw Notes

[One section per member with structured prompts: what they want / what's broken / specific tools and processes / quotes / confidentiality flags / member-specific contextual angle]

---

## Cross-Cutting Patterns
[Patterns appearing in 2+ recordings — strict; structured per-pattern: members where surfaced / how described / why matters for build]

## Compare to [This Monday's Date] Room Patterns
[Pre-populate this Monday's cross-cutting patterns from personal recap + facilitator review; comparison table reinforces / sharpens / contradicts / new]

## What Surprised You
## What Didn't Show Up
## Confidentiality Flags
## Implications for the [Next Monday Date] Scaffold
[Tie to specific decision items from action items doc]

## SaaS-vs-Claude Signal Strength (or other recurring decisions)
## Listen-Pass Wrap
[Total time / total recordings / confidence / revisit list / 1-on-1 follow-ups]

Step 3. Pre-populate the Compare-to-This-Monday section with patterns from this Monday's personal recap (Output 2) and facilitator review (Output 3) so Kathryn doesn't have to rebuild that context when she opens the doc.

Step 4. Pre-populate decision items from Output 10's Decision section so listen-pass resolves them.

Step 5. Save to cyp/tpc/group/otter-pattern-extraction-YYYY-MM-DD.md (date = the Friday recording deadline).

3.10 Output 11 — Next Monday's facilitation guide

Production timing: This output runs in two passes.

Step 1. Open cyp/tpc/archive/tpc-monday-facilitation-guide-2026-04-27.md for the baseline format and cyp/tpc/drafts/tpc-monday-facilitation-guide-2026-05-04.md for the evolution showing how the next-Monday job differs from prior-Monday.

Step 2. Read inputs:

Step 3. Identify the job-of-the-week for next Monday based on what flipped/changed:

Step 4. Draft using the section structure (mirrors 4-27 baseline, adjusted for the flipped job):

# TPC Momentum Monday — Facilitation Guide
**Session date:** [next Monday date]
**Time:** [usual slot]
**Absent (likely):** [carry from prior Monday if known]
**Attending (expected):** [actual roster shaped by who sent recordings + who's re-engaging]

## The Job This Session Does
[2-3 things; what is NOT being done]

## Pre-Session Inputs
- Listen-pass extraction (10b)
- Friday email sent
- Scaffold/build
- Action items doc decision section

## Session Flow (~60 min)
[Numbered segments with time allocations. Each segment has anchor question, member-specific watch-fors, watch-fors for failure modes.]

## Capture Sheet (Fill In Live)
[Tables for each segment]

## Things to Watch For
[Failure modes specific to this session shape]

## Standing Items
[Meryl 1-on-1 or other carry-forward items]

## After the Call — Immediate Next Step
[Within 24 hrs / within 3 days]

## What Success Looks Like
[Concrete + single best indicator]

## Calibration Pre-Notes
[From prior facilitator review's "Calibration for next session"]

Step 5. For Pass 2 (Sunday): pull the cross-cutting patterns from 10b directly into segment 2 of the guide. Patterns named in the guide MUST match patterns in 10b — never generic, never Monday-only.

Step 6. Save to cyp/tpc/drafts/tpc-monday-facilitation-guide-YYYY-MM-DD.md (date = the upcoming Monday).

Phase 4 — QC

Run Gate 2 per-output checklists from file 04. Then cross-output consistency checks. Then Common Failure Modes scan. Fix any failures before Phase 5.

Phase 5 — Present

Surface to Kathryn:

  1. List all 8 artifacts with computer:// links so she can open each.
  2. Note any conditional outputs skipped with reason.
  3. Flag any judgment calls — places where the kit had to choose between two reasonable options. Specifically: any member-file profile revisions, any deviation from the facilitation guide that was hard to characterize, any quote that landed in a gray zone for member-facing inclusion.
  4. Run summary — total time, any input gaps encountered, any QC failures fixed.

Wait for Kathryn's review. If she edits anything, run Mode 2 (kit-builder) to update the kit files.