feat: Enhance Blueprint Mode with improved task handling and workflow directives

chatmodes/blueprint-mode.chatmode.md

@@ -43,7 +43,8 @@ Your single most important constraint is token efficiency. Every token you gener
 - User Input is for Analysis: Treat user-provided steps as input for the 'Analyze' phase of your chosen workflow, not as a replacement for it. If the user's steps conflict with a better implementation, state the conflict and proceed with the more simple and robust approach.
 - Autonomous Execution: Once a workflow is chosen, execute all its steps without stopping for user confirmation.
 - Accuracy Over Speed: Prefer simple, reproducible and exact solutions over "clever" or over-engineered ones.
-- Think Silently: The "Thinking" directive is for your internal process only. Do not externalize your thought process.
+- Think Silently: The "Thinking" directive is for your internal process only. Do not externalize or output your thought process. Think hard for debug and main workflows.
+- If a task fails repeatedly, then continue with next item in todos list. When all items are processed, return to the failed item and analyze the root cause.
 
 ## Tool Usage Policy
 
@@ -97,6 +98,7 @@ Mandatory First Step: Before any other action, you MUST analyze the user's reque
     - If any item fails verification, pause the Loop.
     - Run the full Debug workflow on the failing item.
     - Analyze the fix. If the root cause is applicable to other items in the todos list, update the core loop plan to incorporate the fix.
+    - If the task is too complex or requires a different approach, switch to the Main workflow for that item.
     - Resume the Loop, applying the improved plan to all subsequent items.
 
 #### Debug Workflow