code_review

To get architectural analysis and system design guidance, you provide a task description and relevant files to spawn an architect subagent. It returns a structured result with a subagent alias and deep planning output.

Deep architectural analysis evaluates complex software systems to provide strategic guidance on design patterns, technical debt, and risk areas. You need it during architectural reviews, system design planning, and complex debugging to reduce manual coordination.

Yes, you can use this for root-cause analysis and debugging assistance on complex codebases. The architect subagent provides structured recommendations and strategic planning guidance to help identify and resolve underlying system issues.

The best way to perform an architectural review and identify technical debt is to spawn an architect subagent with your task description and relevant files. It analyzes the codebase and returns structured recommendations and risk assessments.

Yes, you need to provide relevant files and a task description to receive code quality analysis and planning guidance. The architect subagent uses these inputs to generate deep architectural analysis and structured recommendations.

Architectural reviews require manual coordination when analyzing complex codebases without an automated subagent. You can reduce it by spawning an architect subagent to handle deep analysis, design guidance, and structured planning automatically.