Scope: Refactor Acquisition Service Tool and/or Reference Image Manager to improve maintainability, reuse and extensibility. Enable feature migration and reuse across AST, RIM, Sherpa and MiCo, supporting the retirement of Acquisition Monitoring as Service Tool.
Duration: six months, supported by a software engineering mentor and a testing or quality representative.
Deliverables
A working, repeatable workflow and demonstrated software improvement
The architecture of AST has been significantly improved so that it is made more modular, easy to maintain, reusable across different projects and extendable, so that adding extra new functionality can be done faster and more efficiently by the SW teams.
The current functionality and behavior available in AST is maintained, that is, no difference with current solution.
Extensions to the existing testing suit as needed to secure zero regression impact.
Agent instructions, skills, context packages, memory and handover rules.
Linked requirements, designs, code, test plans and execution evidence, meeting the quality expectations and the internal definition of done
Any gaps in requirements, expected behavior, user needs, test plans, test coverage and alike are also identified and raised to the SW teams for them to take action
Comparison with a human-driven baseline and rollout recommendations.
How — Proposed solution
Plan and coordinate. Define tasks, dependencies, agent responsibilities, outputs, completion criteria and human approval gates. An orchestrator routes work, tracks progress and manages changes. Develop test plans alongside requirements and designs.
Provide context and tools. Use existing team requirements, designs, engineering decisions, code examples, standards and known defects. Give agents controlled access to repositories, build tools, automated checks and test environments. Log actions. Shared, versioned memory retains artifacts, decisions and evidence; separate drafts from approved content.
Iterate and check. Each stage follows: read inputs → produce → check → revise → human approval → handover. Agents assess results and adapt using compilation, static analysis, tests and peer feedback. Set iteration, time and cost limits. Escalate ambiguity, repeated failures and decisions outside agent authority.
Communicate and trace. Handovers include versions, requirement references, check results, open questions and approval status. Return failures to the responsible stage and recheck affected downstream work. Changes to requirements or acceptance criteria require human approval.