x-ipe-task-based-refactoring-analysis

To define refactoring scope, analyze initial files and modules to iteratively reveal hidden dependencies, coupling, and documentation gaps across requirements, features, and tests. This produces a concrete boundary and evaluation results to prepare for a structured refactor.

Task-based refactoring analysis evaluates code quality alignment and expands scope boundaries to reveal hidden files and tracing gaps. You need it when starting a refactoring initiative to ensure all dependencies, tech specs, and tests are accounted for before making changes.

Assess code quality alignment by evaluating gaps between current implementation and multi-perspective inputs including requirements, features, tech specs, test coverage, and tracing. This identifies actionable refactoring goals prioritized by principles like SRP, DRY, and KISS.

The best way to identify hidden dependencies is through iterative scope expansion, analyzing initial modules to uncover coupling and documentation gaps across requirements, features, and tests. This yields a final scope with principled constraints to guide next workflow steps.

Yes, you can use this analysis with an initial set of files and modules. Prompt the AI with “Analyze refactoring scope” to begin the workflow, which iteratively reveals dependencies and produces a concrete initial scope, quality evaluation, and actionable refactoring goals.

Your refactoring initiative misses hidden files because the initial scope lacks iterative expansion across requirements, tech design, tests, and tracing. Applying a structured scope analysis reveals these dependencies and documentation gaps to define a complete boundary.