prune-review

A complexity audit evaluates your codebase against specific signals and scale appropriateness guidelines to identify unnecessary risk. It applies six structured prune questions to surface and prioritize areas for refactoring or removal.

The best way to identify refactor risks in a sprint is by applying six prune questions to evaluate codebase signals against scale appropriateness guidelines. This produces a Prune Report with prioritized cut recommendations and escalation paths.

You generate a prioritized cut list by running an on-demand prune audit against the feature, evaluating complexity signals and scale appropriateness. This yields a Prune Report detailing a defined floor and specific cut recommendations.

Yes, you can run a standalone codebase audit without existing lifecycle artifacts. This prune review operates independently, requiring no review.md files and producing no downstream artifacts that other lifecycle phases depend on.

You should request a prune review when you need on-demand assessment of sprint health or codebase-wide complexity. It is explicitly triggered to surface unnecessary complexity and generate a shareable report with escalation paths.