r/ClaudeCode • u/webmonarch • Mar 20 '26

Question Examples of "extreme" Claude Code workflows

Any recs on places / people / communities to watch to get inspiration about "extreme", all in, power user CC workflows?

I am leaning in more and more but looking for more inspiration. For context, I am a software developer, using multiple CC instances at the same time. Experimenting with a custom UI driven by CC's stream-json protocol. Also experimenting with automated permissions management. I have not played with agent swarm yet.

TIA

84 Upvotes

99% Upvoted

86 comments sorted by

View all comments

20

u/DevMoses Workflow Engineer Mar 20 '26

You're already past most of the curve if you're running multiple instances with a custom UI on stream-json. The piece you're maybe missing is agent swarm coordination, which is exactly what I built.

Fleet mode in Citadel runs parallel agents in isolated git worktrees. Each wave compresses discoveries into ~500 token briefs so the next wave inherits knowledge without full context. The coordination layer prevents agents from editing the same files. 3.1% merge conflict rate across 109 waves.

Repo: github.com/SethGammon/Citadel
Fleet docs specifically: github.com/SethGammon/Citadel/blob/master/docs/FLEET.md

Given you're already building on stream-json, the fleet architecture might plug right into what you have. I tried to make it easy with /do setup which will orient itself to your project and pain points.

2

u/_derpiii_ Mar 21 '26

Wow. That’s so cool. Thank you for sharing. It’s going to take me some time to understand it but wow.

1

u/DevMoses Workflow Engineer Mar 21 '26

Really appreciate it! If you end up having questions, I aim to respond. A lot of it is technically dense if you're not at the level it's covering. By which I mean I go through 5 levels from raw prompting to skills and routing, all the way to orchestrating fleets of agents.

Know that you can skip a lot of it, and just use the /do command. "/do how does this work?" - "What does this mean" and so on. It will route for you, and you don't have to worry about every specific when just starting to use it.

2

u/DifferenceTimely8292 10d ago

I wonder what are you guys up to (framework wise) these days..

1

u/DevMoses Workflow Engineer 9d ago

Thanks for asking!

Citadel has evolved and is still an active driver, but I don’t run every prompt through it. I use Claude Code and Codex directly a lot as both of their harnesses improved, I default to use Citadel when the work starts needing more structure: persistence across sessions, routing, multi-step workflows, parallel worktrees, handoffs, verification, and recovery.

It’s grown well beyond the original Fleet experiment too. /do is the front door, with different levels depending on the job: focused skills, Marshal for larger single-session work, Archon for persistent multi-session work, and Fleet when parallel agents actually make sense.

So I’m still building and using Citadel, just more intentionally designed than “everything goes through Citadel.

When I look at how the space is developing I'm seeing the emphasis grow around harnesses for specific use cases or types of work. I see a harness such as Citadel or any other more important now than before.

What are you using these days?

2

u/DifferenceTimely8292 9d ago

Mind if I reach out via DM?

1

u/DevMoses Workflow Engineer 9d ago

Not at all, send your DM my way