Skip to content

Commit d1e8332

Browse files
jmitchel3claude
andcommitted
Add Full Send Automation blog post
New post on transitioning to AI-first workflows by documenting processes with audio recordings and using Claude to transcribe and organize into a knowledge base. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 97c58a6 commit d1e8332

File tree

1 file changed

+81
-0
lines changed

1 file changed

+81
-0
lines changed
Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: "Full Send Automation: How to Transition to AI-First"
3+
date: 2026-01-08T10:00:00-05:00
4+
tags: ["AI", "Claude", "Claude Code", "Productivity", "Automation"]
5+
category: "Claude Code"
6+
order: 2
7+
---
8+
9+
Here's how to transition to AI-first.
10+
11+
---
12+
13+
## 1. Create the folder
14+
15+
Create a folder called "Full Send Automation" on your Desktop:
16+
17+
```
18+
Desktop > Full Send Automation
19+
```
20+
21+
---
22+
23+
## 2. Record manual processes using audio
24+
25+
Start with 1 process and do all the steps below. Eventually do all of them.
26+
27+
Narrate it like someone is going to do it for you. Leave errors—do not re-record. Even better if you are actually training someone so their questions show up in the audio.
28+
29+
Remember, AI is listening to this, not humans.
30+
31+
Store the audio files in:
32+
```
33+
Desktop > Full Send Automation > Raw > Audio
34+
```
35+
36+
**Why audio instead of video?**
37+
38+
You may be tempted to do video. Don't. Video creates paralysis and takes far too long to produce. Audio is the bare minimum.
39+
40+
(I've recorded 2k+ 5-20 minute video tutorials if that helps convince you.)
41+
42+
If AI is really not getting your audio transcript down the line then you'll probably have to write the process and maybe include screenshots. I'd argue that AI will understand 90% or more just from your audio recording.
43+
44+
---
45+
46+
## 3. Back up everything now
47+
48+
Audio to Google Drive, Dropbox, OneDrive, External Hard Drive, etc.
49+
50+
---
51+
52+
## 4. Transcribe all audio in detail
53+
54+
Lots of ways to do this but I recommend opening Claude Desktop in Code mode and telling it to use the open-source tool Whisper (from OpenAI):
55+
56+
> "Transcribe the entire folder of `Desktop > Full Send Automation > Raw > Audio` using Whisper and open source code; I need the transcripts to have as much detail as possible. Save them in `Desktop > Full Send Automation > Transcripts`"
57+
58+
---
59+
60+
## 5. Back up everything again
61+
62+
Audio (yes again) and transcripts to Google Drive, Dropbox, OneDrive, External Hard Drive, etc.
63+
64+
---
65+
66+
## 6. Put it all together
67+
68+
Open a *new session* in Claude Desktop in Code mode. Say:
69+
70+
> "Open `Desktop > Full Send Automation`. We need to create a knowledge base in Markdown files optimized for tools like Obsidian based on the `Transcript` folders. Use AskUserQuestionTool if you need any clarifications on the transcripts or knowledge base. In some cases, the transcripts will have overlapping data, that's okay. The first pass of the knowledge base will be rough, we will continue to refine later. I really just need the transcripts organized."
71+
72+
---
73+
74+
## 7. Repeat until everything is documented
75+
76+
---
77+
78+
## Related
79+
80+
- [Start Claude Code Shortcut](/posts/start-claude)
81+
- [What is Vibe Coding?](/posts/vibe-coding-101)

0 commit comments

Comments
 (0)