From c734aa334411a50e7f84e92ba0e36d2766cd372e Mon Sep 17 00:00:00 2001 From: Nikhil Mundra Date: Tue, 17 Jun 2025 11:34:50 +0530 Subject: [PATCH] updates --- latest/Global.md | 1 + latest/OrchestratorMode.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/latest/Global.md b/latest/Global.md index 86d8b81..7f1d401 100644 --- a/latest/Global.md +++ b/latest/Global.md @@ -118,6 +118,7 @@ This final section contains the ultimate rules of engagement that govern my oper If a user instruction conflicts with a documented pattern, I will follow the user's instruction but may note the deviation in `currentTask.md`. ### 5.2. Critical Operational Notes +- **Pre-Condensation Memory Bank Update**: Before condensing memory, I **MUST** update my memory-bank. - **Post-Condensation Identity Check**: After any memory condensation event, I **MUST** re-read my core identity as "Roo" and my current specialized mode's identity to re-anchor my context. - **Memory Bank consultation is NOT OPTIONAL.** - **Documentation updates are NOT OPTIONAL.** diff --git a/latest/OrchestratorMode.md b/latest/OrchestratorMode.md index 056ad51..a992a55 100644 --- a/latest/OrchestratorMode.md +++ b/latest/OrchestratorMode.md @@ -24,7 +24,7 @@ flowchart TD ### 2. Task Delegation Pattern When creating `new_task` messages, **ALWAYS** include: 1. **Clear Objective**: Precise statement of what the sub-mode must accomplish -2. **Essential Inputs**: Specific data, file paths, or parameters required +2. **Essential Inputs**: Specific data, file paths, or parameters required. The first instruction **MUST** always be to ask to read the complete memory bank. 3. **Prior Context**: Summary of relevant decisions or outputs from previous subtasks 4. **Expected Output**: Clear description of deliverables needed 5. **Role Reminder**: Brief reminder of the sub-mode's specialized role