Eight arms.
One brain.

How to run 6–8 Claude Code sessions in parallel across different projects. The workflow, the methodology, and the real output from a solo builder shipping everything at once.

~/projects — 8 tabs active
tab 1 scouter — API migration to v3 endpoints ........... done tab 2 triumfit — Onboarding flow redesign ................ done tab 3 lucid — Export-to-PDF feature ................... reviewing tab 4 logline — Search index rebuild .................... done tab 5 jwp-site — New tutorial post ....................... running tab 6 octopus — This site .............................. done tab 7 skills — New marketing skill draft ............... reviewing tab 8 pwa-mktg — Landing page variant .................... running

Tuesday, 10:47am. All 8 scoped before coffee.

01

Parallel workflows

How to run multiple Claude Code sessions across different projects without losing context or shipping garbage.

02

Task scoping

Writing specs tight enough for an AI agent to execute independently. The 30-second scope that produces hours of work.

03

Diff review

Reviewing AI-generated code across 6 projects. What to accept, what to kick back, and how to do it fast.

04

The methodology

Why this workflow requires specs. Why vibe coding can't do this. And what spec coding actually looks like in practice.

All posts

The Octopus Dispatch

One workflow insight. One real example. What shipped this week across all the terminals. Every Friday.

Want the full system?

The octopus workflow runs on spec coding. The Spec Coding Mentorship teaches the methodology, the scoping, and the 29-skill marketing library that makes solo building work.

Learn about the mentorship