The mvanhorn Workflow

① Input

🎙️

Monologue

Voice Layer

You speak. It transcribes and types directly into whatever app is focused — usually Ghostty running Claude Code. Transcription doesn't need to be perfect; Claude fills in the gaps.

👻

Ghostty

Terminal — runs Claude Code

4–6 windows open at once. Each is an independent Claude Code session. One plans. One builds. One researches. One debugs. GPU-accelerated so parallel output doesn't lag.

bypass permissions must be on so sessions run autonomously. Sound hook plays when a session finishes.

speech → keystrokes

Claude Code session

② Brain

⚡

Compound Engineering Plugin

The Planning & Execution Engine

Installed into Claude Code. Adds three commands:

/ce:plan — Spins up parallel research agents. Reads your codebase, checks past bugs in plans/, optionally pulls framework docs. Writes a structured plan.md: problem, approach, files to touch, acceptance criteria with checkboxes.

/ce:work — Takes a plan.md and executes it. Breaks into tasks, implements each one, runs tests, checks off criteria. Context lost? Point a new session at the plan and continue.

/ce:brainstorm — Explore an idea before committing to a plan.

reads & writes files on disk

③ Shared Layer (the glue)

💾

Filesystem

The Shared Truth

Both Claude Code and Zed read and write the same files on disk. There's no plugin or bridge between them — the filesystem is the integration. When Claude edits a file, it lands on disk. Zed watches disk. Changes appear instantly.

📋

plans/

Persistent Memory

plans/features/
plans/bugs/
plans/research/
plans/strategy/
plans/archive/

Survives context loss. Survives session restarts. The plan is the checkpoint.

autosave every 500ms ↕ live file watch

open in editor

④ Output — what you see

⚡

Zed

Editor — side by side with Ghostty

Sits on the left half of your screen. Ghostty on the right. Both pointing at the same folder.

Autosave set to 500ms — so when Claude edits a file, you see it appear in Zed line by line in real time. When you type in Zed, Claude sees it within half a second.

No plugin needed. No connection to set up. It's just two apps watching the same files. That's the Google Docs trick.

A single task, start to finish

Monologue

You speak the idea or bug aloud

Ghostty

Speech lands in Claude Code as text. You run /ce:plan

Compound Eng.

Parallel agents research codebase + past plans. Writes plan.md to plans/features/

Zed

Plan appears instantly. You review, edit if needed. Zed saves in 500ms.

Ghostty

You run /ce:work — or switch windows and start the next plan

Zed

Watch Claude write code live. Hear the sound. Review changes. Done.