docs updated

src/modules/bmb/workflows/redoc/instructions.md

@@ -5,6 +5,8 @@
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
 <critical>You MUST have already loaded and processed: {project_root}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
 <critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
+<critical>IMPORTANT: Process ONE document at a time to avoid token limits. Each README should be created individually, not batched.</critical>
+<critical>When using Task tool with sub-agents: Only request ONE workflow or agent documentation per invocation to prevent token overflow.</critical>
 
 <step n="1" goal="Load BMAD conventions and initialize">
 <action>Load ALL BMAD convention documents from {bmad_conventions}:
@@ -69,7 +71,11 @@
 </step>
 
 <step n="3" goal="Process leaf-level documentation" repeat="for-each-leaf-item">
-<action>For each individual workflow folder in execution plan:
+<critical>TOKEN LIMIT WARNING: Process ONE item at a time to prevent token overflow issues.</critical>
+<critical>If using Task tool with sub-agents: NEVER batch multiple workflows/agents in a single invocation.</critical>
+<critical>Each README creation should be a separate operation with its own file save.</critical>
+<critical>Sequential processing is MANDATORY - do not attempt parallel documentation generation.</critical>
+<action>For each individual workflow folder in execution plan (PROCESS ONE AT A TIME):
 1. Read ALL files completely:
    - workflow.yaml (metadata, purpose, configuration)
    - instructions.md (step structure, goals)
@@ -94,9 +100,11 @@
    - Focus on DISTINCTIVE features, not boilerplate
 
 4. Save README.md to workflow folder
-   </action>
 
-<action>For each individual agent file in execution plan:
+<critical>If multiple workflows need documentation, process them SEQUENTIALLY not in parallel. Each workflow gets its own complete processing cycle.</critical>
+</action>
+
+<action>For each individual agent file in execution plan (PROCESS ONE AT A TIME):
 
 1. Read agent definition file completely:
    - XML structure and metadata
@@ -229,6 +237,7 @@
 - Any catalog files created
 - Files skipped or requiring manual review (if any)
 - Coverage: X% of items documented
+- Processing notes: Confirm sequential processing was used to avoid token limits
   </action>
 
 <action>Display summary to user</action>