type: skill status: active scope: all-clients

Post-Session Production Kit — Skill

This is the full end-to-end workflow for processing a client session. It starts when the transcript is available and ends when every action item is drafted, scheduled, or calendared. The advisory email is one output — not the whole job.

Trigger

Session transcript (.txt) and JSON (.json) are available in the client's sessions/ folder.

Required Inputs

Before starting, confirm you have:

1. Session transcript (.txt) — ground truth. Read this, not a relay recap or processed summary.
2. Session JSON (.json) — speaker-level timing, metadata. Read alongside the transcript.
3. Client reference data — reference-data/[client]-reference-data.md. Load FIRST. Every proper noun in the email gets checked against this.
4. Prior advisory email — the last email sent to this client. Voice and format reference.
5. Client CLAUDE.md — engagement context, active projects, constraints.
6. Active project plans — current build statuses, action items carried forward.

If any of these are missing, stop and get them before proceeding. Do not draft from memory or processed recaps.

Phase 1: Read and Extract (Do Not Write Yet)

1.1 Read the full transcript

Not skim — read. Cover to cover. You are looking for:

• What actually happened — decisions made, things shown, things agreed to
• Exact quotes worth anchoring — things the client said that reveal thinking
• Commitments — anything the client or Kathryn said they would do
• Emotional signals — what energized the client, what they resisted, what they glossed over
• New information — things that weren't known before this session
• Corrections to prior understanding — things that contradict what's in the project plans or CPM

1.2 Cross-reference against reference data

Every name, every tool, every org mentioned in the transcript — check against the reference data. Transcripts misspell names. The reference data is canonical. If you find a new name or org not in the reference data, add it.

1.3 Extract action items into two lists

Client action items:

• What did the client commit to doing?
• What was assigned to the client explicitly?
• What does the client need to provide before the next session?
• For each item: is it AOS engagement work, or is it the client's own business operations? Only AOS engagement work goes in the email. Client's own operations go in the email ONLY if they're tied to a build or constraint.

Kathryn's action items:

• What did Kathryn commit to doing?
• What needs to be built, researched, drafted, or scheduled before the next session?
• For each item: can it be done now (draft it), or does it need a deep work block (schedule it)?

1.4 Identify friction points in client action items

For each client action item, ask:

• Is this easy for the client to do? (30 seconds, grab a file, forward an email)
• Is this hard? (Requires finding something buried, creating something new, redacting, thinking through something complex)
• Can Kathryn reduce the friction? (Do the redaction, search the inbox, draft a template, prep questions)

Produce a friction analysis. Items where Kathryn can help get drafted as a follow-up email or folded into the main advisory email.

Phase 2: Draft the Advisory Email

2.1 Select the right skill

• Paying client (e.g., Jenn, Ruben) → use advisory-client-email-SKILL.md
• Coachee (e.g., Pooja) → use session-recap-email-SKILL.md

2.2 Assemble the email

Follow the selected skill. Key reminders:

• Opening: 1-2 sentences. One specific moment from the call. Don't summarize.
• Wins: Factual bullets. No editorializing.
• What We Covered: One line per topic. Compressed. Not the transcript reformatted.
• Action items grouped by owner. Client items: "Before our next session:" framing. Kathryn items: third person.
• Next session date + proposed agenda.
• Closing: Warm, specific, not motivational.
• Subject line: [Topic]: [M-DD-YYYY] format.

2.3 Fold in the golden examples list or friction-reduction items

If the session produced a list of artifacts the client needs to provide, or if Kathryn can help reduce friction on the client's action items — include that in the email or draft a companion email. Don't make the client hunt through two emails when one would do. But don't make the main email so long the action items get buried.

Rule of thumb: If the list is 3 items or fewer, fold it into the main email. If it's 4+, send it separately and reference it in the main email.

2.4 Format for Gmail

The email must be copy/paste ready for Gmail. That means HTML — not Markdown. Produce an .html file with inline styles that renders correctly when pasted into a Gmail compose window.

Phase 3: Self-QC

Run the full QC checklist (qc-checklist-advisory-client-email.md or qc-checklist-session-recap-email.md) before declaring the email ready.

Additionally:

• [ ] Reference data cross-check. Every name in the email matches the reference data. Every org is spelled correctly. Every tool is named correctly.
• [ ] Action items are AOS engagement work only. Nothing that's the client's own business operations unless tied to a build or constraint.
• [ ] No relay recap dependency. Every claim in the email traces to the transcript, not a processed summary.
• [ ] Friction analysis complete. Every client action item assessed for difficulty. Kathryn's help offered where it reduces friction.
• [ ] Kathryn's action items are real commitments. Nothing fabricated. Only what was committed to in the session or logically follows from the session.
• [ ] Read the email aloud. Does it sound like Kathryn or like AI? If any sentence sounds like a LinkedIn post, rewrite it.

Phase 4: Action Item Execution

Do not stop at the email. The email is a communication — it doesn't do the work.

4.1 Draft everything that can be drafted now

For each of Kathryn's action items:

• Can it be drafted right now? (Follow-up email, concept brief, research summary, template) → Draft it. Put it in drafts/.
• Does it need a deep work block? (Building a kit, running an extraction, designing a build) → Don't draft it. Schedule it.

4.2 Schedule deep work blocks

For action items that need dedicated time:

• Create a calendar event with:
• Clear title: what's being built
• Description: what inputs are needed, what the output is, where it goes
• Duration: realistic estimate
• Place it before the next session — Kathryn needs to show up prepared.

4.3 Schedule follow-ups

For items that require checking in with the client:

• If there's a specific follow-up date mentioned in the session ("I'll check in two weeks") → create a calendar event or reminder
• If there's a deadline the client committed to → create a reminder for the day after to check status

4.4 Schedule the next session prep

Create a calendar event 24-48 hours before the next session:

• Title: "[Client] — session prep"
• Description: review all action items, confirm what's done, prep agenda
• This is the trigger for the next cycle.

Phase 5: File Management

5.1 Move the sent email to archive

Once Kathryn confirms the email was sent:

• Move .md and .html from drafts/ to archive/
• Any companion emails (friction-reduction, golden examples list) → same move

5.2 Move processed inputs

If any inputs were consumed during this process (client docs from inputs/, constraint briefs):

• Move to archive/ with a note on what they fed

5.3 Update project plans if needed

If the session changed build statuses, revealed new constraints, or shifted timelines — flag it. Don't update the project plans inside this workflow (that's a separate workflow step). But note what needs updating so it doesn't get lost.

Outputs Checklist

At the end of this workflow, the following should exist:

• [ ] Advisory email — sent (or in ready/ awaiting Kathryn's send)
• [ ] Companion emails — sent or in drafts/ (friction-reduction, golden examples, etc.)
• [ ] Kathryn's action items — each one either drafted or scheduled
• [ ] Follow-up reminders — in Google Calendar
• [ ] Deep work blocks — in Google Calendar
• [ ] Next session prep — in Google Calendar
• [ ] File moves — drafts archived, inputs archived
• [ ] Flags for other workflows — noted (CPM update needed, project plan update needed, etc.)

What This Skill Does NOT Cover

• CPM updates (Step 1 in the weekly workflow)
• Master plan updates (Step 2)
• Project plan updates (Step 3)
• Blueprint updates (Step 4)
• Builds (Step 5)

This skill is Step 6 — but it's Step 6 done completely, not just the email.

Golden Examples

• aos-client-jb/archive/jenn-advisory-email-2026-03-27.html — Jenn 3/27/2026. Full advisory email with wins, compressed topics, action items by owner, proposed agenda, personal close. Companion friction-reduction email sent separately.
• Ruben golden examples referenced in advisory-client-email-SKILL.md