performance-orchestrator

Static code analysis identifies N+1 queries, O(n^2) algorithms, and blocking I/O by scanning your codebase. It orchestrates a structured workflow covering specification, planning, implementation, and verification to systematically resolve detected performance bottlenecks.

Yes, you can optionally integrate user-provided profiling data into the performance optimization workflow. The orchestrator combines this data with static analysis to detect memory leaks and missing indexes, then outputs structured results under .maister/tasks for review.

A phase-driven pipeline coordinates multi-agent analysis and fixes by reusing existing framework patterns. It initializes phase tasks and state, executing specification, planning, implementation, and verification stages to manage artifacts and structure improvements.

Yes, the workflow supports flexible orchestration with interactive or automated YOLO execution modes. You can start an automated performance optimization workflow by providing a task description that outlines the bottleneck and your optimization goals.

Static analysis is needed when you must proactively detect memory leaks, blocking I/O, and missing database indexes before runtime issues occur. It provides bottleneck detection across codebases without requiring live application traffic or active profiling sessions.