Roadmap & Cleanup: IntelliManage status, unused docs, and mode toggles in Roo Commander

[OleynikAleksandr]

Hi Jez,

first of all, thank you for sharing Roo Commander with the community.
We tried adopting it in a production-like workflow and hit a few
practical obstacles that make everyday use difficult. Could you please
clarify the roadmap?

Key pain points we see today

1. IntelliManage still missing
   Documentation heavily references an IntelliManage core (setup guide
   DOC-SETUP-GUIDE-001, !pm commands, automatic artefact creation),
   but there is no working implementation in the public repo.
   Question: Is IntelliManage actively developed? Do you have a rough
   ETA for a usable release, or is it on hold?

2. Large amount of dormant material
   .ruru/docs/* and many template artefacts come with the clone, yet
   are not used without IntelliManage. They increase repo size, slow
   indexing and confuse new users.
   Suggestion: consider moving them to a separate branch / archive
   until the feature is ready.

3. 102 built-in modes inflate every prompt
   Enabling all modes by default blows the token budget and makes the
   Orchestrator choose between overlapping roles. A simple per-project
   UI or even a YAML toggle to activate only the required modes would
   help a lot.
   Request: could you provide a native way (GUI or schema field) to
   disable unused modes without forking Roo Code?

In short, we would like to understand whether the project is still
active and when to expect:

• a functioning IntelliManage core (even MVP);
• official guidance on trimming unused folders/files;
• a built-in mechanism to select the minimal set of modes.

If the feature set is unlikely to arrive soon, a lighter “clean” fork
(without the dormant docs and modes) would already make Roo Commander
easier to integrate.

Thanks for your time and for any visibility you can share!

Best regards,
Oleksandr Oliinyk

[jezweb]

1. I parked it while i worked on getting a better implementation of the prompts among other things. WHen i was working through the detailed I realised I would need some kind of session / state management so I ended up working on that instead.
2. yep, it was initially some thinking aloud. I've been putting more recent ideas in this branch: https://github.com/jezweb/roo-commander/tree/v8.0.0
3. I agree, have been a bit torn with this from the start. The current thought I have and partly why I've been spending time trying to learn how to make effective agents in n8n ( https://creators.n8n.io/workflows/4547 and and https://n8n.io/workflows/4559-intelligent-web-and-local-search-with-brave-search-api-and-google-gemini-mcp-server/ was with the view that i could take all of the planning/tasking parts of roo commander out of roo code so that it doesnt mess up the context. My experience with using builder in ai studio and firebase studio i think shows that less hand holding back and forth is preferable.
4. Yes, active but slow because i decided i need to learn how to use mcp servers and agents better so that I could bring those ideas back into roo commander.
5. thank you for taking the time to write.

[OleynikAleksandr]

Hi Jeremy!

Thank you so much for your response.

I apologize for not noticing the v8.0.0 branch earlier:
https://github.com/jezweb/roo-commander/tree/v8.0.0

I will review the ideas presented there and get back to you.
Thanks again!

Aleksandr.

[OleynikAleksandr]

Subject: Thoughts on Roo Commander's Development

Hi Jez,

First and foremost, I want to express my sincere admiration for your work. You've created an incredibly deep and well-thought-out system of 102 modes, each representing a complete tool with detailed instructions and a knowledge base. This is truly impressive work!

However, while observing the project, I've noticed that this rich functionality remains inaccessible to most users due to navigation complexity. I believe your developments deserve a much wider audience and practical application.

I'd like to propose the following reorganization plan:

1. Roo Commander Mode (Primary Focus)
   Codebase Optimization:
   Remove unused files and folders related to IntelliManage
   Keep only what's necessary for the modes to function
   User Experience Improvements:
   Mode Initialization - automatic detection and loading of modes from .roomodes
   Intuitive Gallery with categorization by frameworks/functions
   Favorite Collections - create and save custom sets of modes
   Quick Loading of selected modes into Roo Code
   Mode Constructor - simple interface for creating custom modes based on templates

2. IntelliManage (Separate Project)
   Move to an independent repository
   Develop separately from the main branch
   Consider future integration with Roo Commander Mode
   I'd be happy to help with the UI/UX development - I already have some preliminary work in this direction. If you're open to it, I'd like to implement the UI Manager part within your project rather than as a separate fork of Roo Commander. I'd really like to make Roo Commander more accessible to everyone.

P.S. The topic of n8n automation is also interesting to me, but I'd prefer to discuss it separately. I'll gather my thoughts and share my perspective on the challenges faced by developers of tools like Cursor, Windsurf, Roo Code, and Copilot - where the prompt size sent with each user message keeps growing while response quality declines.

With respect and admiration for your work,
Aleksandr

[jezweb]

Thank you, I appreciate it. Yep that sounds ok to me. I did try and cull everything that didn't seem necessary from the build files and to make a core set of nodes so that people don't have to have all of them install but to my fault i didnt check if all the excess modes were left out and so it appears they all ended up in all the builds.
https://github.com/jezweb/roo-commander/releases/tag/v7.3.0
eg this was supposed to be a much smaller set of modes.
https://github.com/jezweb/roo-commander/releases/download/v7.3.0/roo-commander-coll-core-CollectionBuild.zip
The whole repo needs to have a broom put through it. Aside from all the other things Roo Commander has been a learning experience in how to use github in a public way and the first time ive been responsible for releases, branches, etc, as that would usually be something I'd leave to a developer to manage. Hence many mistakes, inconsistencies and perhaps unconvential choices.

Happy to remove all the intellimanage stuff, it was full of good intention and lacked execution.

If you would like to help more directly i'd be open to that too, im happy for you to message me on the discord group or email me / google chat: jeremy@jezweb.net if you like. I suspect a lot of what you are suggesting exceeds my abilities to deliver without developer help.

[OleynikAleksandr]

Hi Jez,

Thank you so much for your response! I really appreciate your openness and willingness to collaborate.

Would it be possible for you to create a separate repository with a clean version of Roo Commander Mode that includes only the Modes along with their Instructions and KB, excluding all folders and documents related to the IntelliManage project? Additionally, a brief Readme for this new project would be incredibly helpful.

I'd love to start working with this streamlined version, and I'll be sure to share my progress with you once I have something to show.

Looking forward to your thoughts!

Best regards,
Aleksandr

[jezweb]

Sure! Great idea, lets do that