Symphony handles issue→code. What handles idea→issue?

[AutoJunjie]

We built Chorus, it’s basicly Symphony with a "idea → spec → task DAG" layer. support Openclaw as a PM live in slack channel, support all coding agent via Skill and with Pixel office view, check it out: https://github.com/Chorus-AIDLC/Chorus

[AutoJunjie]

[jaeko44]

Nice one boi

Check out bosun as well (virtengine/bosun)

I'm gonna borrow your task dag thing because I was looking for a way to implement tasks with sub tasks and yours seems like a really good approach

[ChenNima]

Thanks! Really glad you found the task DAG idea useful 🙂

Feel free to take inspiration from it. Just a quick note that the project is licensed under AGPL-3.0, so if any code ends up being reused or adapted, the AGPL terms would apply.

Either way, happy it sparked some ideas

[jaeko44]

I dont copy code, I just reimplement the concept - your code is safe and wont even be read.

[kumanday]

I was just thinking of & wanting to work on this and propose AI-DLC. I love the task DAG and visualization layers, but AGPL creates serious license contamination (triggers copyleft obligations, as stated by the OP). The original AI-DLC repo is MIT-licensed and would be a much better candidate for flexible implementations.

Options include:

• submitting PRs to AI-DLC for Linear as a task management substrate beyond Markdown files
• creating a new AI-DLC derivative MIT-licensed project
• creating an Agent Skill to convert the Markdown task files into Linear issues

I think the third option has the least friction and I was planning on doing that work anyway. I'll report my progress and experience with that :-)

[AutoJunjie]

Glad that you like the AI-DLC methodology. With Chorus, we actually plan our proposal object actually can adopt any spec method, which give out flexibility for enterprise to build their own.

Cant wait for your full AI-DLC workflow & linear integration, would love to see that.