Your system · one recording, everything else

The session you already ran is the content

An add-on for people whose real work happens live: client sessions, workshops, group calls, live builds. Record the session once, and one recording becomes the transcript, the clean video cut, the podcast with show notes, a recap page your participants can revisit, and post drafts in your own spoken voice. Nothing gets performed for the camera, and every piece waits for your yes.

Add it to your system

It reads the system you already built and slots in. No full system yet? It brings a small starter and runs on its own.

See the difference

The same session, two afterlives

The session that vanished into a folder, and the session that keeps working. Flip between them.

The session that vanished
TUESDAY, 4PM: YOUR BEST SESSION IN WEEKS

Someone had a breakthrough. You explained the thing better than you ever have. The recording landed in a Zoom folder, next to forty others nobody has opened since the day they were made.

Then Thursday arrives, the calendar says "make content", and you sit down at a blank page to perform a smaller version of what you already did brilliantly on Tuesday.

The session that keeps working

The same Tuesday recording, run through the set: a transcript on your machine, a clean cut of the video, the session as a podcast episode with show notes, a recap page your participants revisit, and a week of post drafts built from the moments you actually said.

Thursday's "make content" slot becomes a review: you read the drafts, keep what sounds like you, resolve the consent flags, and post. The blank page never happens, because the content already happened, live, on Tuesday.

Every derived piece is built from what you actually said in the session, so it sounds like you because it is you.

The whole flow

From one recording to everything you publish

Six moves that live inside your own system. The session does the creating; the set does the shaping; you do the posting.

1
Record

The session you were running anyway

A client session, a workshop, a live build. Press record, run it the way you always do, and drop the file in when it ends. That is the whole creative act, and you already did it.

2
Transcribe

Locally, on your own machine

One script turns the recording into a timestamped transcript and subtitles. It runs locally, so a 60-minute session takes real minutes, and your clients' voices never leave your computer.

3
Cut

A clean cut of the video

Trim the dead start and end, drop the sections that should not survive, add captions if you want them. You approve the plan before anything gets cut, and the original stays untouched.

4
Recap

A page your participants revisit

What the session covered, in your phrasing, with the video and the links in one place. Built from a template that slots into the site you made in Module 6.

5
Podcast

Clean audio plus show notes

The session as an episode: loudness-normalized audio, notes drafted from the transcript with timestamps pointing at the moments, and one chosen link.

6
Posts

The drafts wait for your yes

The 3 to 5 moments that actually landed, each drafted as a post that keeps your spoken phrasing. They sit in a folder until you review them, and you post them yourself.

One recording at a time, the whole set

The flow finishes one session's set before the next recording goes in. That is a deliberate rule, because a folder of forty half-processed recordings is the old problem wearing a new outfit. One session in, its video, page, episode, and posts out, then the next.

❤️

The live session is the engine

Your best explanations happen when a real person is in front of you, and that is exactly the material this works from. It is a Heart practice: the connection creates the content, and the system it lives in is yours.

The part that makes it yours

It sounds like you because it is you

Generic content tools write from a template of what usually works. This works from a transcript of what you actually said, to real people, in a real session.

Your spoken words are the source

Derived text keeps your phrasing and your rhythm. "It kind of clicked when you said it out loud" stays that sentence, in the recap, in the notes, in the post. A line you did not say never gets written for you.

Participants get consent care

Anything showing or quoting a participant gets flagged before it goes anywhere public: who appears, in which piece, and whether their okay exists yet. The people who trusted you with a live session stay protected in the afterlife of it.

Drafts wait for you

Every piece is shown to you as a draft and stops there. You review, you edit, you post, on whatever platform you already use. It cannot upload or publish anywhere, and that is a feature.

What it will honestly tell you it cannot do

Editing here means clean cuts, trims, and captions: it is a kitchen knife, and its job is a clean cut rather than motion graphics or jump-cut montages. Transcription runs locally, so a 60-minute session takes real minutes, and the trade is that your clients' voices never leave your machine. And it cannot upload or publish anywhere: you post, by design, after the drafts and the consent flags have had your eyes on them.

A peek inside

What you are adding

Plain files that drop into your root system, in folders you own and can open in anything.

# record-it-once/ drops into .claude/commands/ and your root
record-it-once.mdthe one skill: transcript first, one question, then the chosen set in order: the cut, the recap, the podcast, the posts
transcribe-session.shlocal transcription: recording in, timestamped transcript and subtitles out, uploaded nowhere
recap-page.template.htmlthe recap page, self-contained, built to slot into your Module 6 site
CLAUDE.md (starter)a minimal root, so it runs standalone if you do not have the full system
README.md + SETUP-GUIDE.mdthe overview and the install, add-on or standalone

The promises

The rules it never breaks

Built the same way as the rest of your system, because your clients' trust is on the line.

Nothing is performed for the camera

It works from the session you already ran, exactly as you ran it. The recording stays untouched, and cuts are always new files.

Your phrasing survives every format

The transcript is the source for the recap, the notes, and the posts. When a draft needs a sentence you did not say, it asks you instead of writing one.

Participants get consent care

Anything with a participant in it, a face, a name, a quoted line, gets flagged for their okay before it goes anywhere public. No okay, no publish suggestion.

Publishing stays yours

Every derived piece is a draft on your machine. It cannot upload, schedule, or post anywhere. You review, then you post, wherever you already publish.

How to use it

Drop it in, then bring it one real recording

Install takes about 10 minutes. Transcription runs on its own, and each draft afterwards is minutes to review.

1

Drop it into your system, plus one extra install

Download and unzip into your root folder. The skills join your existing skills. The one extra piece is ffmpeg, the tool that does the cutting: one brew install line, and the install takes a few minutes. The transcription tool installs itself on its first run.

2

Bring the recording from last week

The session sitting in your Zoom folder right now is the perfect first one. Say "I recorded a session": the transcript gets made locally, then one question asks what you want from it: the cut, the recap page, the posts, the podcast, or everything.

3

Work through the set, then post

The chosen pieces run in order: the cut, the recap, the podcast, the posts. Review each draft, resolve the consent flags, and publish wherever you already do. Then the next recording goes in.

# one line in your root CLAUDE.md, once - Record It Once: when a new session recording lands or I say "cut this recording", read the record-it-once skill and run it.

Your next session is already the content.

Record the one you were going to run anyway, drop the file in, and let one recording become the video, the podcast, the page, and the posts. The work you do live keeps working after the call ends.

Add it to your system

Want to build it live with us instead? Come to the next live session.