improve

You generate implementation plans by auditing a codebase in read-only mode to produce prioritized, self-contained handoff plans that other agents execute without modifying source code.

A codebase audit for tech debt and bug hunts is a read-only analysis that identifies high-value improvements across security, performance, and test gaps to produce prioritized implementation plans for other agents.

You create self-contained handoff plans by surveying a repository and generating documents with clear scopes, steps, verification gates, and drift checks that target a universal plans directory for executor compatibility.

Yes, you can use read-only codebase analysis for large repository migrations to generate prioritized, self-contained implementation plans that guide product direction and team alignment across multiple agents.

The best way to prioritize code improvements is to audit the codebase to highlight the highest-value changes, generating actionable plans with explicit drift checks and verification steps for executor compatibility.

You should not use an automated planning agent when your workflow requires direct source code editing, as this approach enforces a strict no-edit rule and only outputs handoff plans to a plans directory.