body-overview

Legacy body overview requests are automatically routed by a compatibility layer that directs them to either ad-hoc synthesis or structured periodic review workflows. This ensures older health dashboard queries are handled without breaking.

The best way to handle backward compatibility for full body report requests is using a routing layer that redirects legacy phrases to modern analysis workflows, preventing broken user interactions without duplicating specialist logic.

Yes, the legacy routing layer supports both by intelligently redirecting requests to body-data-qa for ad-hoc synthesis or body-cadence-review for structured periodic reviews, depending on the user's needs.

You need a compatibility layer for health overview routing when older routing models are still in use, ensuring that requests phrased as body overview or health dashboard are correctly directed to appropriate modern workflows.

Your body overview request avoids duplicating specialist logic because the compatibility layer relies entirely on downstream workflows for data pulling, goal analysis, and resource searching rather than processing the data itself.

Yes, you can use this routing layer to handle explicit legacy phrases without breaking user interactions, as it seamlessly directs older full body report requests to the most suitable analysis skill.