department setup

[Jim8Knopf]

I'm currently thinking of a 'department' setup. Would this also be a future setup case for your clawdboss?
What i think with departs is that you don't have one coding agent. Instead you have one that catches the idea and writes the issue, a second one that develops it and a third that test the development and complains when its not done properly.
Similar comcepts could also work for the other busines departments. My idea was to mimic the actual reallive structure in a company.

[Jim8Knopf]

What do you think about this idea?

[dempseydata]

Several “systems” for Claude code take similar approaches such as https://github.com/gsd-build/get-shit-done But you might want something slightly less weighty. It depends on your goals

[Jim8Knopf]

Several “systems” for Claude code take similar approaches such as https://github.com/gsd-build/get-shit-done But you might want something slightly less weighty. It depends on your goals

That sound pretty intresting. I'll defenetly try it out. Do you think it's possible to combine it with oc or is this a bad idea?

[dempseydata]

The general concept of defining what needs to be built, confirming it, planning it, incrementally building it, and then testing it, is a good idea. BUT…. What is the complexity level where working directly in Claude Code is far better? One option is to enable OC to work with the CC CLI, in a space where GSD is setup. The OC job then becomes defining the work to be done in a manner that is optimal for input to CC/GSD. This way, OC effectively becomes the conversational go between with you and CC. Fully embedding GSD in OC might be a bit too much of a token burner…. May be offer two options: configure GSD for OC, or install GSD in a separate folder and ask the user to set up CC CLI for that folder

…

On Sun, Mar 15, 2026 at 09:58 Jim Knopf ***@***.***> wrote: *Jim8Knopf* left a comment (NanoFlow-io/Clawdboss#1) <#1 (comment)> Several “systems” for Claude code take similar approaches such as https://github.com/gsd-build/get-shit-done But you might want something slightly less weighty. It depends on your goals That sound pretty intresting. I'll defenetly try it out. Do you think it's possible to combine it with oc or is this a bad idea? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAU762ZRH3YDOQZ6DECAGND4Q2ZJHAVCNFSM6AAAAACWSJ6SF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANRTGA2DKNBSGI> . You are receiving this because you commented.Message ID: ***@***.***>

[NanoFlow-io]

Interesting idea! The department/team structure concept — having separate agents for issue writing, development, and testing — is definitely something being considered. It aligns well with how ClawDBoss already supports specialist agents (comms, research, security), and extending that to a full development workflow pipeline is a natural next step.

Thanks for the suggestion, leaving this open for discussion.

[dempseydata]

Sounds like a plan