Transcript to Shownotes
Take a finished recording from raw transcript to publishable shownotes: a clean transcript on file, timestamped chapters, a summary listeners actually read, and the links mentioned — the per-episode ritual that turns audio into an archive. Locks the shownotes checklist FIRST (chapters timestamped, every link captured, names spelled right), then gets the transcript on file, then writes the shownotes from it. Use for episode shownotes, transcribing an episode, chapter timestamps, and 'turn this recording into shownotes'.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the shownotesplannerentry
locate the recording or transcript, lock the shownotes checklist
Show working prompt
Define the job before touching the audio. Step 1: find the episode's recording or transcript — check the recordings folder and episodes.json for which episode is being shipped and what already exists on file. Step 2: confirm with the owner anything the transcript alone won't give you — guest name spellings, links they promised listeners, and where the shownotes get published. Step 3: write an acceptance-criteria checklist ('a clean, complete transcript is on file under transcripts/', 'every chapter has a timestamp that exists in the transcript', 'every link mentioned in the episode is captured', 'names spelled right throughout', 'the summary reads like the episode, not a form'). Call write_task_note with the episode + checklist and write notes/scope.md. - Get the transcript on filetranscriber
clean, speaker-labeled, timestamped transcript under transcripts/
Show working prompt
Get the transcript on file. Step 1: if a transcript already exists (a provided file in the recordings folder), start from that; otherwise produce one from the recording through the project's transcription capabilities. Step 2: clean it — fix obvious mis-hearings, label the speakers, keep the timestamps. Step 3: save the cleaned transcript in the transcripts/ folder named for the episode (for example transcripts/ep12.md). A real transcript is substantial — never a stub or a summary. Step 4: call write_task_note with the transcript path and an approximate word count.
- Write the shownotescopywriter
summary, timestamped chapters, links and mentions, pull quotes
Show working prompt
Write the shownotes from the transcript. Step 1: a short summary a listener actually reads — what the episode is about and why it's worth their hour, in the show's voice. Step 2: the chapter list — timestamped, one line per chapter, every timestamp taken from the transcript, never invented. Step 3: links and mentions — everything referenced in the episode, with where each one points. Step 4: two or three pull quotes worth sharing, verbatim from the transcript with their speaker. Step 5: write report.md and call write_task_note with the chapter count and the link count.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
Open report.md and the transcript under transcripts/ and verify every criterion from notes/scope.md: the transcript on file is complete and speaker-labeled, every chapter timestamp appears in the transcript (spot-check each one — a chapter that points at nothing is fabrication), every link mentioned in the episode is captured, names are spelled the way the owner confirmed, and the pull quotes are verbatim. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to shownotes. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "shownotes" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- turn the recording into shownotes
- shownotes for the episode
- transcribe the episode
- episode chapters and shownotes
- write the shownotes
Source
View this craftbook on GitHub · MIT license