new-refactor

To scope a refactoring opportunity, analyze code smells, complexity, coupling, and missed abstractions across modules to plan structural improvements. This process produces a structured brief covering the Problem Statement, Affected Code, Current State Analysis, Target State, Scope, Risks, and Success Criteria.

The best way to plan structural code improvements is by diagnosing concrete problems across files, functions, and patterns, then proposing actionable scope and a target state. This approach evaluates risks and defines success criteria to ensure existing functionality remains intact during the refactor.

Analyze code complexity and coupling by reading the relevant codebase to diagnose structural issues like duplication and tight dependencies. Building context from project conventions and prior refactors grounds the analysis, ensuring the proposed target state aligns with existing architectural patterns.

Yes, you can use this refactoring approach for any software engineering project needing maintainability and extensibility improvements. The session adapts to your specific codebase by reading project conventions and code before proposing measurable, actionable structural changes.

A structured refactoring brief is needed because it defines the Problem Statement, Scope, Risks, and Success Criteria before changes are made. This prevents unplanned scope creep and ensures that structural improvements to complexity, duplication, and coupling are measurable and impactful.

You should not use a comprehensive scoping process for simple, isolated code fixes that lack cross-module complexity, coupling, or missed abstractions. This structured approach is designed for impactful refactors requiring a detailed Target State, Scope, and Risk Assessment.