---

name: episode-architecture
description: "Transform a raw recorded episode into a structured show asset with narrative momentum, chapter markers, and the one moment that drives shares."

/episode-architecture

Raw recordings meander. The best insight arrives 43 minutes in. The guest circles back to clarify something they said in minute 12. There's a seven-minute tangent that was fun in the room and bewildering on playback. Listeners who zone out don't come back — they just stop subscribing. A show that doesn't get shared doesn't grow. The difference between an episode that generates word-of-mouth and one that doesn't is almost never the quality of the conversation — it's whether someone did the structural work afterward to find the narrative and make it unmissable. This skill does that work.

Core Insights: 3-5 Worth Remembering

• After reviewing the transcript or notes, name the 3-5 insights that are genuinely worth a listener's time. Not topics discussed — insights. An insight has a specific claim and a reason it's true.
• Bad: "We talked about hiring."
• Good: "The first hire should reduce the founder's cognitive load, not add capability — the business can't absorb capability it hasn't earned."
• For each insight, write it in one sentence that could stand alone on social. If you can't compress it to one sentence, it isn't an insight yet — it's still a discussion.
• If you found more than 5, cut. An episode with 8 "key insights" has none.

Narrative Sequence: Build Momentum, Don't Just Order Chronologically

• Map the insights against the recording timestamps. They probably didn't arrive in the right order.
• Find the sequence that builds: each insight should deepen or complicate the previous one. The listener should feel like they're building toward something.
• Identify the structural arc: What's the tension at the start? What's the resolution at the end? Every memorable episode has both.
• Name what gets moved, cut, or repositioned. If a tangent doesn't serve the arc, flag it as a cut — don't try to integrate it.

Chapter Markers with Timestamps

• Produce chapter markers in the format: [HH:MM:SS] Chapter Title
• Chapter titles must be specific enough to navigate by — "The hiring mistake most founders make at Series A" not "Hiring discussion."
• Chapters serve two purposes: navigation for the listener, and indexable content for SEO and platforms. Both require specificity.
• Minimum chapter length: 4 minutes. Maximum: 12. If a chapter would be shorter than 4 minutes, it belongs inside the adjacent chapter.

The "So What" Per Insight

• For each of the 3-5 core insights, add one line: what should the listener do or think differently because of this?
• The "so what" is the bridge between an interesting idea and a useful episode. Without it, smart conversations feel like entertainment rather than value.
• Write it as a directive: "Before your next hiring conversation, ask: does this role reduce my cognitive load or add a capability I haven't earned yet?"

The Shareable Clip Moment

• Name the single 60-90 second moment in the episode that works as a standalone clip — no context needed to understand it, emotionally resonant, ends with a complete thought.
• Specify the exact timestamp range.
• Write the caption that would run under it on LinkedIn or Instagram Reels: one sentence that names the insight, one sentence that makes people watch.

The Single Takeaway

• Write the one thing a listener would say to a colleague tomorrow when asked "what's the best thing you've heard lately?" If it can't be said in one sentence, the episode didn't land.
• This is also the subtitle for the episode — not the guest's name and credentials, but the thing they said that's worth remembering.

Rules

1. Insights require a specific claim. Topics are not insights.
2. Narrative sequence overrides chronological order. Move content if the arc demands it.
3. Chapter titles must work as navigation, not decoration.
4. One shareable clip. Not three candidates — the best one.
5. The single takeaway is written for the listener's conversation, not the producer's podcast description.
6. Cuts are part of the output. Name what doesn't serve the episode.

The output is a complete show architecture document — chapter markers, core insights with "so what," the clip timestamp, and the episode title — that a producer can hand directly to an editor and a social team.