My Claude Code Workflow: Terminal, Boards, and Screenshots

I run multiple projects in parallel with Claude Code. Not one session at a time — multiple sessions, across multiple workstreams, for hours at a stretch. It took me a while to figure out how to actually manage that without losing track of things. Here's where I landed.

The split that made everything click

The biggest unlock was separating strategy from execution.

I do strategic planning — goals, milestones, "what are we trying to achieve and why" — in my project files. That's where the thinking lives. But I needed somewhere else for the day-to-day execution. What am I doing today? What's in progress? What's next?

That's where the task board comes in. I have a Planner board with lanes: Today, In Progress, On Deck, Done. Plus workstream boards for each project area. Strategy flows down into board cards. Board progress feeds back into reviews.

Claude reads both. It knows the strategic context and the execution state. It can flag when my daily work is drifting from the bigger goals — or confirm I'm on track.

Starting a session

I open the workflow terminal, a new tab fires up, Claude auto-launches and reads my CLAUDE.md. First thing it does is read the board and my last session buffer — so it knows what I was working on last time, and what's on the board right now.

If I've got a specific task, I'll send the card straight from the board into the session. Open the card, hit "Send to Session," pick which session gets it. Claude has the full task description without me typing anything.

Parallel workstreams

On any given day I'll have 3-5 sessions running across different projects. One building a feature, another fixing something, maybe a third scoping out a new idea. This is where things used to fall apart — you lose track of which session is doing what, which one is waiting on you, which one's been idle for ten minutes.

The session monitor fixes that. It's a floating HUD showing every active session — status, project, context health. I can see at a glance what needs me. When a session is waiting for input, I switch, respond, move on. When one is running low on context, I know to wrap it up before it starts making mistakes.

Micro efficiencies compound

This is the theme that runs through everything. In this new world of building with AI, you're moving fast. Claude is often waiting on you more than you're waiting on it. Every unnecessary step, every extra context switch, every piece of friction — it compounds across an 8-hour day.

The screenshot tool is a perfect example. One hotkey, the screenshot drops straight into whichever terminal I'm on. No Finder, no paste, no wrong-key fumbling. I see a UI issue, I capture it, Claude already has it. That loop should be instant — and now it is.

End of session

When I'm wrapping up, I move completed cards to Done, note anything that needs to carry forward, and close the session. If there are board updates — new tasks that surfaced, cards to move — I handle those quickly. Clean state for next time.

It all loops back to the split: the board tracks what I'm doing, the project files track why I'm doing it, and Claude reads both. No duplication. No drift. Strategy flows down, execution flows up.

The tools

Everything here is part of Claude Code Toolkit — one menu bar app, four tools. $24, one-time, runs entirely on your machine. If you're running multiple Claude sessions across real workstreams, this is the workflow layer that was missing.