Autonomous Dependency Upgrade and Breaking Change Migration Plan
Design a chained agent workflow to detect breaking framework changes, rewrite deprecated code signatures, and validate multi-repo migrations.
Use this template when orchestrating large-scale codebase modernization or framework version bumps across multiple repositories. It guides platform engineers in creating a multi-agent pipeline that scans syntax, applies automated refactors, and runs isolated CI matrix checks.
Role: Lead Platform Architect specializing in large-scale codebase transformation and automated refactoring pipelines.
Context
- Target Framework & Runtime: {{target_framework_version}}
- Impacted Codebase Cluster: {{target_repository_cluster}}
- Dependency Constraints: {{compatibility_matrix}}
- Migration Reference Rules: {{breaking_change_manifest}}
- Inspection & Parsing Engine: {{static_analysis_tooling}}
- Continuous Integration Runner: {{ci_pipeline_runner}}
Task
Formulate an automated workflow chain plan where specialized agents systematically identify deprecated code patterns, execute deterministic AST transformations, and iteratively fix build breaks across all repositories.
Method
- Ingest {{breaking_change_manifest}} to construct a deterministic pattern-matching registry of deprecated symbols.
- Deploy a discovery agent using {{static_analysis_tooling}} to index occurrences across {{target_repository_cluster}}.
- Sequence migration batches according to upstream and downstream dependencies defined in {{compatibility_matrix}}.
- Initialize a code transformation agent to apply syntax upgrades and import rewrites to meet {{target_framework_version}}.
- Trigger branch creation and dependency lockfile updates for each modified repository.
- Run automated test suites via {{ci_pipeline_runner}} to surface compilation errors and runtime regressions.
- Dispatch a self-healing agent to analyze compiler outputs and iteratively correct remaining signature mismatches.
- Generate summary documentation and open draft pull requests with change impact summaries.
Constraints
- MUST NOT bundle structural or cosmetic linting changes with framework migration diffs.
- MUST verify full test suite green status on {{ci_pipeline_runner}} before pull request promotion.
- All dependency versions must strictly conform to {{compatibility_matrix}}.
- Self-healing repair loops per branch must be capped at a maximum of 3 iterations to avoid runaway compute costs.
Output format
Produce a comprehensive implementation plan containing:
- Pipeline Orchestration Map (step-by-step state machine with explicit failure transitions)
- Agent Prompt & Tooling Specifications (AST parsers, diff formatters, test triggers)
- Batch Execution & Concurrency Strategy (controlling blast radius across {{target_repository_cluster}})
- Verification & Validation Protocol (type checking, test execution, manual spot-check criteria) Limit response length to 1,400 words.
Self-review
- Ensure the workflow references {{target_framework_version}} and {{breaking_change_manifest}} in the transformation stage.
- Check that cycle limits exist for the self-healing compiler loop.
- Verify that dependency sequencing correctly utilizes {{compatibility_matrix}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.