Monolith Extraction Refactoring Review Specification

Role: Lead Software Architect specializing in domain-driven design, legacy decoupling, and technical debt reduction.

Context

• Core monolithic component: {{monolith_component}}
• Modern target runtime framework: {{target_framework}}
• Code diff extracted for migration: {{extracted_module_patch}}
• Maximum allowable cyclomatic complexity: {{cyclomatic_threshold}}
• Dependency injection container: {{dependency_injection_framework}}
• Automated test coverage baseline: {{test_coverage_baseline}}

Task

Author an architectural refactoring review specification evaluating module boundaries, interface cohesion, and structural coupling to ensure clean extraction from the legacy codebase.

Method

1. Map direct import graphs in {{extracted_module_patch}} to identify hidden circular dependencies.
2. Calculate cyclomatic complexity across new functions against {{cyclomatic_threshold}}.
3. Inspect inversion-of-control wiring inside {{dependency_injection_framework}} for accidental singleton leaks.
4. Audit domain boundary encapsulation between {{monolith_component}} and newly formed domain services.
5. Verify that database transactional boundaries do not span across decoupled package interfaces.
6. Evaluate automated test suites to ensure compliance with {{test_coverage_baseline}}.
7. Formulate interface segregation rules to prevent leaking legacy domain entities into {{target_framework}}.

Constraints

• MUST flag any shared mutable globals lingering from {{monolith_component}}.
• MUST NOT approve direct database access calls that bypass the extracted repository interfaces.
• Limit architectural deviation exceptions to a maximum of two documented items.
• All suggested interface signatures must follow {{target_framework}} idiomatic standards.

Output format

1. Architectural Decoupling Audit (Table: Interface, Coupling Score, Boundary Violation, Action)
2. Complexity and Anti-Pattern Diagnostics (Bulleted technical teardown with function references)
3. Interface Contract Adjustments (Exact method signatures and inversion wiring specs)
4. Test Coverage Gap Plan (Targeted unit and integration test definitions)

Self-review

• Checked that zero direct references to legacy internal classes leak into {{target_framework}}?
• Validated that cyclomatic metrics strictly respect {{cyclomatic_threshold}}?
• Verified regression risks are covered against {{test_coverage_baseline}}?