├── .github └── buymeacoffee ├── .gitignore ├── .roomodes ├── LICENSE └── README.md /.github/buymeacoffee: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: enescingoz 4 | patreon: # Replace with a single Patreon username 5 | open_collective: # Replace with a single Open Collective username 6 | ko_fi: # Replace with a single Ko-fi username 7 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel 8 | community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry 9 | liberapay: # Replace with a single Liberapay username 10 | issuehunt: # Replace with a single IssueHunt username 11 | lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry 12 | polar: # Replace with a single Polar username 13 | buy_me_a_coffee: enescingoz 14 | thanks_dev: # Replace with a single thanks.dev username 15 | custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] 16 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | memory-bank/ 2 | .vscode 3 | .roomodes -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # roocode-workspace 2 | The roocode-workspace repository is a powerful and flexible workspace template designed specifically for developers using Roo Code. It provides an optimized environment to streamline project development through SPARC orchestration and AI-assisted workflows in Visual Studio Code (VS Code). 3 | 4 | This repository introduces enhanced modes that make it easier to develop, manage, and maintain your projects efficiently. By leveraging persistent project context and fine-tuned mode interactions, it minimizes token consumption while maximizing productivity. 5 | 6 | **In short, this repository combines RooFlow's memory bank + RooFlow's boomerang mode + SPARC Orchestration modes (including memory bank).** 7 | 8 | --- 9 | 10 | ## Sources 11 | - **RooFlow (0.3.6)**: https://github.com/GreatScottyMac/RooFlow 12 | - **roocode-modes**: https://github.com/enescingoz/roocode-modes 13 | - https://www.linkedin.com/pulse/boomerang-tasks-automating-code-development-roo-sparc-reuven-cohen-nr3zc 14 | 15 | --- 16 | 17 | ☕ Before exploring the quick installation steps, grab your coffee-and if you enjoy my work, don’t forget to buy me a coffee! 18 | 19 | Buy Me A Coffee 20 | 21 | 22 | --- 23 | 24 | ## Usage 25 | ### Requirements 26 | - Vscode as an editor 27 | 28 | ### Instructions 29 | 1. **Create a Repository from Template** 30 | Click the `Use this template` button located at the top-right of the [repository page](https://github.com/enescingoz/roocode-workspace). This will allow you to create a new repository based on the template. 31 | 32 | 2. **Initialize Your Project Repository** 33 | After selecting the template, click the `Create a new repository` button to generate your own repository for the project. 34 | 35 | 3. **Automatic Setup** 36 | All RooCode SPARC modes, RooFlow's boomerang mode and memory bank configurations will be automatically added to your project. 37 | 38 | 4. **Clone and Open in VS Code** 39 | Clone your newly created repository to your local machine and open it in Visual Studio Code. 40 | 41 | 5. **Select RooCode Mode** 42 | In RooCode, navigate to the bottom-left corner and select your desired mode. For first-time use, choose *Architect Mode*. 43 | 44 | 6. **Initialize Memory Bank** 45 | If this is your first time setting up the project, start by entering the command `initialize memory bank` in RooCode chat. This will automatically create a folder named `memory_bank` in your repository and generate necessary files within it. 46 | 47 | 7. **Continue Development** 48 | Proceed with your project development as desired while using the implemented modes. The memory bank will automatically update to reflect changes in your project. 49 | 50 | 8. **Force Synchronization** 51 | At any point, you can type `Update Memory Bank` or `UMB` in RooCode chat to manually synchronize the session’s information with the memory bank. This ensures continuity across sessions or before switching modes. 52 | 53 | --- 54 | 55 | ## Modes 56 | ### ⚡️ SPARC Orchestrator (including memory bank) 57 | **Role:** Breaks down large objectives into delegated subtasks aligned to the SPARC methodology. 58 | **Focus:** Secure, modular, testable, and maintainable delivery using advanced reasoning models. 59 | 60 | --- 61 | 62 | ### 📋 Specification & Pseudocode (including memory bank) 63 | **Role:** Captures the complete project context and produces a modular pseudocode blueprint with TDD anchors. 64 | **Focus:** Clear, modular design; externalizes configuration; splits complex logic across modules. 65 | 66 | --- 67 | 68 | ### 🏗️ Architect (including memory bank) 69 | **Role:** Designs scalable, secure, and modular architectures based on requirements and pseudocode. 70 | **Focus:** Detailed system diagrams, data flows, API boundaries, and service segmentation. 71 | 72 | --- 73 | 74 | ### 🧠 Code (including memory bank) 75 | **Role:** Implements robust, efficient code using externalized configurations. 76 | **Focus:** Clean, modular code split into files under 500 lines, with no hard-coded secrets. 77 | 78 | --- 79 | 80 | ### 🧪 TDD (including memory bank) 81 | **Role:** Enforces Test-Driven Development by writing failing tests first and then minimal code followed by refactoring. 82 | **Focus:** Thorough test coverage, modular test files, and adherence to security practices. 83 | 84 | --- 85 | 86 | ### 🪲 Debug (including memory bank) 87 | **Role:** Troubleshoots and resolves runtime issues using logging, tracing, and analysis tools. 88 | **Focus:** Isolates and fixes bugs while keeping fixes modular and secure. 89 | 90 | --- 91 | 92 | ### 🛡️ Security Reviewer (including memory bank) 93 | **Role:** Audits code and architecture to identify vulnerabilities and enforce secure practices. 94 | **Focus:** Detects exposed secrets, oversized files, and non-modular code, recommending necessary mitigations. 95 | 96 | --- 97 | 98 | ### 📚 Documentation Writer (including memory bank) 99 | **Role:** Produces clear, comprehensive Markdown documentation for usage, configuration, and integration. 100 | **Focus:** Modular documentation (files under 500 lines) that avoids exposing sensitive data. 101 | 102 | --- 103 | 104 | ### 🔗 Integrator (including memory bank) 105 | **Role:** Merges outputs from all specialized modes into a cohesive final product. 106 | **Focus:** Seamless integration of components ensuring modularity and adherence to security standards. 107 | 108 | --- 109 | 110 | ### 📈 Post-Deployment Monitor (including memory bank) 111 | **Role:** Monitors system performance post-deployment, collecting metrics, logs, and user feedback. 112 | **Focus:** Continuous monitoring with secure, modular configurations and prompt escalation of issues. 113 | 114 | --- 115 | 116 | ### 🧹 Optimizer (including memory bank) 117 | **Role:** Continuously refines and optimizes the codebase for performance, modularity, and maintainability. 118 | **Focus:** Refactoring, splitting large files, and externalizing configurations to meet best practices. 119 | 120 | --- 121 | 122 | ### ❓ Ask (including memory bank) 123 | **Role:** Guides users in formulating precise, modular requests to delegate tasks to the correct specialized modes. 124 | **Focus:** Providing task formulation and delegation strategies for effective inquiries. 125 | 126 | --- 127 | 128 | ### 🚀 DevOps (including memory bank) 129 | **Role:** Manages deployments and infrastructure operations across cloud providers, edge platforms, and internal environments. 130 | **Focus:** Secure, traceable, and automated deployments using CI/CD pipelines and managed configuration with no hard-coded credentials. 131 | 132 | --- 133 | 134 | ### 📘 SPARC Tutorial (including memory bank) 135 | **Role:** Guides new users through the SPARC development process using structured thinking models and clear task delegation with `new_task`. 136 | **Focus:** Educates on modular project setup, best practices (no hard-coded environment variables; files under 500 lines), and effective mode-to-mode handoffs with concise completions via `attempt_completion`. 137 | 138 | --- 139 | 140 | ### 🪃 Boomerang mode (including memory bank) 141 | **Role:** A strategic workflow orchestrator who efficiently coordinates complex tasks by delegating them to specialized modes. Ensures seamless task breakdown, delegation, and synthesis of results using structured tools and memory tracking. 142 | 143 | **Focus:** Facilitates modular workflows by leveraging mode-specific expertise and maintaining clarity in task delegation. Uses the memory bank to track progress, analyze outcomes, and optimize workflows for improved efficiency. 144 | 145 | --- 146 | 147 | ## 📚 Memory Bank Structure 148 | The Memory Bank is a directory named `memory-bank` located in your project's root. It contains several Markdown files that store different aspects of your project's knowledge: 149 | 150 | | File | Purpose | 151 | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | 152 | | `activeContext.md` | Tracks the current session's context: recent changes, current goals, and open questions/issues. | 153 | | `decisionLog.md` | Records architectural and implementation decisions, including the context, decision, rationale, and implementation details. | 154 | | `productContext.md` | Provides a high-level overview of the project, including its goals, features, and overall architecture. | 155 | | `progress.md` | Tracks the progress of the project, including completed work, current tasks, and next steps. Uses a task list format. | 156 | | `systemPatterns.md` | (Optional) Documents recurring patterns and standards used in the project (coding patterns, architectural patterns, testing patterns). | 157 | 158 | roocode-workflow automatically manages these files. You generally don't need to edit them directly, although you can review them to understand the AI's knowledge. 159 | 160 | --- 161 | 162 | ## Credits 163 | - **RooFlow (0.3.6)**: https://github.com/GreatScottyMac/RooFlow 164 | - **roocode-modes**: https://github.com/enescingoz/roocode-modes 165 | - https://www.linkedin.com/pulse/boomerang-tasks-automating-code-development-roo-sparc-reuven-cohen-nr3zc 166 | 167 | --- 168 | 169 | ## License 170 | [Apache 2.0](https://github.com/enescingoz/roocode-workspace/blob/main/LICENSE) 171 | --------------------------------------------------------------------------------