Architecture Technical Debt Refactoring Operational Brief

Role: VP of Engineering Operations and Principal Enterprise Software Architect

Context

• Target Codebases & Services: {{legacy_service_inventory}}
• Performance & Scaling Chokepoints: {{throughput_bottlenecks}}
• Code Quality & Maintainability Signals: {{cyclomatic_complexity_reports}}
• Competing Product Roadmap Demands: {{quarterly_feature_commitments}}
• Infrastructure & Cloud Cost Ceilings: {{infrastructure_budget_cap}}
• Reliability & Performance Targets: {{target_sla_targets}}

Task

Draft a technical debt refactoring brief that justifies and operationalizes targeted architectural remediation while protecting delivery commitments and remaining within defined infrastructure constraints.

Method

1. Cross-reference {{legacy_service_inventory}} with {{cyclomatic_complexity_reports}} to locate high-churn, high-risk modules.
2. Quantify the operational drag imposed by {{throughput_bottlenecks}} on ongoing release cadence and system concurrency.
3. Evaluate the risk profile of deferred refactoring against the reliability goals set in {{target_sla_targets}}.
4. Align candidate refactoring phases with {{quarterly_feature_commitments}} to mitigate scheduling collisions.
5. Model resource allocation to ensure refactoring tasks respect {{infrastructure_budget_cap}}.
6. Structure a phased migration path using patterns such as strangler-fig or anti-corruption layers.
7. Define explicit cutover triggers, rollback criteria, and automated verification benchmarks for each phase.

Constraints

• MUST justify every refactoring initiative with measurable engineering metrics (e.g., MTTR, deploy frequency, error budgets).
• MUST NOT propose full ground-up rewrites without incremental, deployable operational phases.
• Budget and roadmap trade-offs MUST be stated explicitly with mitigation plans.
• The output must follow strict concise brief formatting under 650 words.

Output format

Generate the brief using these required sections:

• Strategic Architectural Context
• Operational Drag & Vulnerability Assessment
• Phased Refactoring Roadmap (Phase, Target Component, Decoupling Strategy, Deliverable)
• Resource Allocation & Delivery Risk Trade-Offs

Self-review

• Ensure every architectural claim connects back to operational risk or performance.
• Verify that each phase yields independently deployable system increments.
• Confirm all 6 input variables are logically integrated.