Software Deliveryapibatch

Legacy module modernisation: analysis, tests, rewrite, PR

Starts from a Jira epic; the old module is read, its behaviour pinned with tests, rewritten and opened as a PR with evidence.

In short

Legacy module modernisation: analysis, tests, rewrite, PR is an agent scenario in the Software Delivery sector running on the api, batch channels. Trigger: A "modernisation" epic pulled into the sprint in Jira. The Modernisation Supervisor coordinates 4 specialist agents (Analysis Agent, Test Agent, Developer Agent, Review Agent) across 4 systems (Jira, Git (self-hosted), CI Pipeline, Static Analysis); of 10 steps, 3 write to systems and 2 are checks or approvals. Outcome: Characterisation tests green, new module passes the same tests, PR under review. Approval rule: Production schema change or out-of-scope file → architect approval; PR merge always human.

Software Delivery

Legacy module modernisation: analysis, tests, rewrite, PR

run #41,288,528elapsed 0 mstokens 0est. cost $0.000status —Approval rule: Production schema change or out-of-scope file → architect approval; PR merge always human

Agents in this run

Modernisation Supervisorsupervisorplans, routes, approves

Analysis Agentaginies-tulpar-4 · on-premMaps the old module's dependencies and behaviour, writes the risks

Test Agentaginies-sunkar-1 · Code AginiesPins current behaviour with characterisation tests

Developer Agentaginies-sunkar-1 · Code AginiesRewrites the module in the target architecture and makes the tests pass

Review Agentaginies-tulpar-4 · on-premChecks security, performance and out-of-scope changes

Audit trail00:00.00

Epic SRV-2210: "move the collections calculation module from Java 8 to a service", 14 files, 6,800 lines
Call graph extracted: 3 external dependencies, 2 shared tables, shared use with the nightly batch
Design note: behaviour boundaries, 4 risky calculation branches, out-of-scope files listed
Plan: characterisation tests → green → rewrite → same tests → static analysis → PR
212 characterisation tests generated; 91% coverage on the old module, 3 ambiguous branches flagged
Expected behaviour of the 3 ambiguous branches asked of the product owner; answer in a Jira comment
Module rewritten as a service; 212/212 tests pass, p95 latency 180 ms → 62 ms
Static analysis clean; 1 out-of-scope file change reverted; no secret leakage
PR #4471 opened: design note, test report, performance comparison and rollback plan attached
Jira epic set to "in review"; architect and team lead assigned as PR reviewers
■completed

Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus

Trigger

A "modernisation" epic pulled into the sprint in Jira

Outcome

Characterisation tests green, new module passes the same tests, PR under review

Agents

SUPERVISOR

Modernisation Supervisor

Decomposes the objective, delegates to agents, manages approval points, merges the result.

aginies-tulpar-4 · on-prem

Analysis Agent

Maps the old module's dependencies and behaviour, writes the risks

read_repocall_graphwrite_design_note

aginies-sunkar-1 · Code Aginies

Test Agent

Pins current behaviour with characterisation tests

generate_testsrun_testscoverage_report

aginies-sunkar-1 · Code Aginies

Developer Agent

Rewrites the module in the target architecture and makes the tests pass

edit_filesrun_testsopen_pr

aginies-tulpar-4 · on-prem

Review Agent

Checks security, performance and out-of-scope changes

static_analysisdiff_reviewrequest_changes

Steps

#	Kind	Agent	What happens	System	ms	tok
01	ingest	Modernisation Supervisor	Epic SRV-2210: "move the collections calculation module from Java 8 to a service", 14 files, 6,800 lines	Jira	200	—
02	retrieve	Analysis Agent	Call graph extracted: 3 external dependencies, 2 shared tables, shared use with the nightly batch	Git (self-hosted)	2,800	2,400
03	reason	Analysis Agent	Design note: behaviour boundaries, 4 risky calculation branches, out-of-scope files listed	—	2,400	1,800
04	plan	Modernisation Supervisor	Plan: characterisation tests → green → rewrite → same tests → static analysis → PR	—	260	240
05	write	Test Agent	212 characterisation tests generated; 91% coverage on the old module, 3 ambiguous branches flagged	CI Pipeline	3,600	2,900
06	approval	Modernisation Supervisor	Expected behaviour of the 3 ambiguous branches asked of the product owner; answer in a Jira comment	Jira	400	—
07	write	Developer Agent	Module rewritten as a service; 212/212 tests pass, p95 latency 180 ms → 62 ms	Git (self-hosted)	3,900	3,600
08	verify	Review Agent	Static analysis clean; 1 out-of-scope file change reverted; no secret leakage	Static Analysis	1,500	900
09	write	Developer Agent	PR #4471 opened: design note, test report, performance comparison and rollback plan attached	Git (self-hosted)	600	—
10	notify	Modernisation Supervisor	Jira epic set to "in review"; architect and team lead assigned as PR reviewers	Jira	300	—

Simulation metrics (estimated)

1,900runs / month

90.4%success

16 sp50

$0.0189est. cost / run

Approval rule

Production schema change or out-of-scope file → architect approval; PR merge always human

Step profile

ingest · 1plan · 1retrieve · 1reason · 1verify · 1approval · 1write · 3notify · 1

SYSTEMS

Jiraticketing
Git (self-hosted)api
CI Pipelineapi
Static Analysisapi

What you need to run it

API access and assignment rules for the ticketing or work-order system
Credentials and a test environment for the enterprise APIs involved
An authorised role and approval channel for the approval rule (mobile approval card, e-mail or ticket)
SSO with the organisation’s identity provider and a scenario-specific authorisation group

Global pattern

The agent-assisted rewrite pattern in large banks' and telcos' core modernisation programmes

Packages that include this scenario SDLC agent team → Sector: Software Delivery →

Related agents

Software DeliveryHITL

Feature delivery pipeline

A Jira epic turns into criteria, design, code and tests via agents; humans only review and approve the PR.

1,200 runs / month 91.2% success 5 agents

Software DeliveryHITL

CI/CD release pipeline

Build, tests, scans and staging run unattended; production ships only on release-manager approval, via ArgoCD.

950 runs / month 94.7% success 5 agents

Software DeliveryHITL

Incident response and hotfix

Alert fires, bug reproduced, patch and regression run ready; on-call approves, post-mortem already drafted.

320 runs / month 90.5% success 5 agents

Time to move from experimenting with AI to transforming with it.

In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.

Book a 30-minute discovery session → dahi@aginies.com

Your 2–3 priority problems
Live demo of a similar scenario
Roadmap starting with value analysis