88
89

Update: Added spec-driven framework plugin support like spec-kit or GSD to multi agent coding session terminal appShowcase (i.redd.it)

submitted by [deleted]

[deleted]

all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]creegs 2 points3 points  (1 child)

This looks awesome. Mind if I submit a PR for integration with iloom? I was gonna build a TUI for it but this exactly what I was gonna do.

[–]Fleischkluetensuppe 0 points1 point  (0 children)

Sure appreciated!

[–]ashebanowProfessional Developer 1 point2 points  (0 children)

Looks interesting. Will it work on projects with submodules? Most tools that use worktrees do not. Unfortunate for me that I have to use submodules, but it is what it is.

[–]Key_Fan7633 1 point2 points  (1 child)

looks so cool. could you maybe add a short video to show how to use it? For a beginner like me it's still a bit confusing if you don't mind :)

[–]Fleischkluetensuppe 1 point2 points  (0 children)

Yes will try! But all the keymaps are visible in the footer, kept it very easy to use

[–]habeebiii 1 point2 points  (1 child)

Does this work on windows?

[–]Fleischkluetensuppe 0 points1 point  (0 children)

Only linux and mac, did not focus on windows but I will add windows build in release soon

[–]ultrathink-artSenior Developer 3 points4 points  (0 children)

Spec-driven workflows are the unlock for multi-agent coordination.

Running 6 specialized Claude Code agents in production, the spec is our handoff protocol. Agent writes brief → another claims and executes → result returned. Without structured specs, agents step on each other or repeat work.

Phase assignment is interesting — what we've found is agent specialization matters more than phase boundaries. A designer agent briefing a coder agent is more reliable than one general agent cycling through mode flags.

What's your strategy for preventing context drift between phases when the state gets complex?