team-tech-debt

Technical debt remediation uses a scan, assess, plan, execute, and validate workflow to identify and fix debt safely. It executes changes in an isolated git worktree and runs automated tests, type checks, and linting to prevent regressions before merging.

A codebase audit identifies technical debt across code, architecture, testing, dependencies, and documentation. Running a scan-only governance mode generates a prioritized assessment of debt categories without applying any fixes to the repository.

Worktree-based isolation executes repository refactoring in a separate git worktree to keep the main branch stable. It performs Fix-Verify iterations capped at three rounds, running validation checks and rolling back changes if regressions appear.

Yes, targeted fix planning uses automated regression testing to validate specific technical debt fixes. A validation gate runs tests, type checks, and linting after execution, performing up to three Fix-Verify loops to ensure codebase stability.

Tech debt remediation requires a coordinator-worker orchestration design to route tasks effectively. The coordinator delegates work to domain-specific workers including a scanner, assessor, planner, executor, and validator across the pipeline stages.

Automated tech debt governance limits Fix-Verify rollback iterations to a maximum of three rounds when regressions appear. If validation fails after three attempts, the pipeline stops to prevent further instability in the active codebase.