← 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 output. 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 the session prep doc (if one exists)

Look in cyp/tpc/drafts/tpc-monday-prep-YYYY-MM-DD.md and cyp/tpc/events/*/. Note: the stated job, what was explicitly NOT being done, the segments, per-member watch-fors.

Full facilitation guides were discontinued 2026-06-22 (too detailed) and are not coming back. Some weeks there is no prep doc at all. If there isn't one, note that in the run summary and proceed — do not block, and do not invent a plan to measure the session against.

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/group/[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 Do not stop to confirm

Self-advancing. Proceed straight to Phase 2. Stop only if the transcript is missing, multiple transcripts match, or the source is genuinely ambiguous — a missing prep doc is not one of those.

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 the session prep doc (if one exists) to the 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/group/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/group/tpc-momentum-monday-YYYY-MM-DD.md.

3.3 Output 3 — Facilitator review

Step 1. Open cyp/tpc/group/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 session prep doc'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/group/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/group/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/group/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

Source of truth: cyp/tpc/planning/tpc-friday-email-rules.md — codified 2026-05-29 from Kathryn's actual edits across 5 weeks, updated 2026-06-12. It governs the Friday email's delivery, voice, and structure. Follow it exactly. If it ever conflicts with this kit, the rules file wins — flag the conflict in the Mode 2 wrap-up.

What the Friday email actually is (do not reinvent it): a recurring "Weekly Review and Preview" template. Almost all of it — the weekly review/preview form, the 1-on-1 link, the "on tap this week" calendar, the "coming up next" retreat block, the signature, the footer — already lives in Kathryn's MailerLite template. The only thing this output drafts is the personal message section (the short note at the top). Do NOT draft a job-of-the-week, a single "ask," deeper-question options, an opener→recap→ask→logistics narrative, or "verify/Do-NOT" lists. That narrative shape is retired — it never matched what Kathryn sends.

Step 1 — Read first, draft once (rules 8–9). Before writing a word: (a) the most recent shipped Friday email — pull it from MailerLite (getcampaign on the latest TPC: Weekly Review and Preview campaign; read the HTML body, not plaintext) or fall back to cyp/tpc/archive/; (b) the most recent transcript in cyp/tpc/transcripts/; (c) planning/tpc-friday-email-rules.md. Attribute member specifics to the transcript, never the recap.

Step 2 — Draft only the personal message section, in the rules-file structure:

Write it in plain, paste-ready prose — NOT markdown bold/headers (they don't paste into MailerLite). Apply the forbidden-terms list from the rules file.

Step 3 — Save to cyp/tpc/drafts/tpc-friday-email-YYYY-MM-DD-skeleton.md with the header below. Preferred final path per the rules file: Kathryn copies last week's MailerLite campaign and edits it directly — this skeleton is the personal-message starting point, not a finished email.

Step 4 — Mandatory header on the skeleton:

Personal message section only. Paste into the MailerLite "Weekly Review and Preview" template — the form, calendar, retreat block, signature, and footer are already there; do not redraft them. Source of truth: planning/tpc-friday-email-rules.md. Voice anchors: the most recent shipped Friday email + the latest transcript.

3.9 Output 11 — Next Monday's prep doc

Step 1. Open cyp/tpc/events/2026-07-in-person/mm-2026-07-20-operating-week.md and cyp/tpc/drafts/tpc-monday-prep-2026-07-27.md for the shape. Both are ONE PAGE. Match that length.

Step 2. Read this Monday's personal recap (Output 2) and facilitator review (Output 3) — especially "Calibration for next session." That section is the spine of the prep doc.

Step 3. Name the job for next Monday in 2–3 sentences, and name what is NOT being done. If the prior Monday left something unfinished, that is usually the job.

Step 4. Draft:

# Momentum Monday — [Month DD, YYYY] · [Short session name]
**Virtual group call · 9:00 AM ET · Facilitator: Kathryn**
**[One line: what this session is.]**

## Why this session
[2-3 sentences. The job, and what it is NOT.]

## Run it
[Segments with rough minutes. Short bullets.]

## Watch for
[Per-member notes that matter THIS week. Not everyone every week.]

## Decisions to land
[Pointers to group/tpc-action-items-YYYY-MM-DD.md]

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

Do NOT produce a full facilitation guide — flow scripts, anchor questions per segment, capture-sheet tables, pull-in prompts per member. That format was discontinued 2026-06-22 as too detailed and is not coming back.

Output 12 — Notion board writes (final step, Review-first)

The last step of the run. Two destinations, two shapes — write both. Internal boards only (not member-facing — this does not violate "drafts only / don't send").

A. KHB Operations — the run's open-items card (one per run).

B. TPC Member Pipeline — per-member signal update. (Private board — never shared with members.)

Rule — facts auto, reads proposed. The cascade writes the factual fields on both boards automatically; it proposes lane/read changes and waits for Kathryn.

Acceptance: open-items card on KHB Operations (Workstream TPC, every item linked); each present member's Pipeline row has updated Last touch + appended Signal/why; lane/read shifts surfaced (not auto-applied); both board links returned.

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 every artifact 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 session prep doc 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.