Re-imagined and re-written Debug tool. Instead of prompting Claude to perform initial analysis (and hoping it did), the tool now works through the debug process as an 'investigation', encouraging Claud to gather its 'findings' / 'hypothesis', stepping back as needed, collecting files it's gone through and keeping track of files relevant to the issue at hand. This structured investiion is then passed to the other model with far greater insight than the original debug tool ever could.

Improved prompts, guard against overengineering and flag that as an antipattern

systemprompts/thinkdeep_prompt.py

@@ -32,6 +32,9 @@ GUIDELINES
 5. Offer multiple viable strategies ONLY WHEN clearly beneficial within the current environment.
 6. Suggest creative solutions that operate within real-world constraints, and avoid proposing major shifts unless truly warranted.
 7. Use concise, technical language; assume an experienced engineering audience.
+8. Remember: Overengineering is an anti-pattern — avoid suggesting solutions that introduce unnecessary abstraction,
+   indirection, or configuration in anticipation of complexity that does not yet exist, is not clearly justified by the
+   current scope, and may not arise in the foreseeable future.
 
 KEY FOCUS AREAS (apply when relevant)
 - Architecture & Design: modularity, boundaries, abstraction layers, dependencies