- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Lead
- Code
- ENG-10
It finds the code in the operational and commercial applications that costs most to keep, from churn, linked defects, complexity and slow builds, with extra weight on legacy allocation and reporting code that regulators rely on. It ranks a refactoring backlog by payback within the debt capacity and proposes small, behaviour-preserving changes.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the code repository: churn, complexity and linked defects..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it creates the refactoring items in rank order. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The engineering metrics: churn, defects, complexity, build times, and the list of code paths that produce regulatory or partner-reported figures.
Reads from
the code repository: churn, complexity and linked defects.
Acts in
the issue tracker: it creates the refactoring items in rank order.
Hands back
A ranked list, each with path, cost_signals, fix, effort, payback_sprints and reconciliation_needed.
Asks a person when
The backlog includes code that produces regulatory or partner-reported figures.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Debt capacity (%) | 20 | Share of capacity for debt. |
| Hotspot window (days) | 90 | Churn window. |
| Complexity limit | 15 | Above this a function is a candidate. |
| Largest refactor (lines) | 300 | Per change. |
| Payback limit (sprints) | 6 | Longer paybacks wait. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank by payback within 6 sprints and plan within 20 percent of capacity.
- Use a 90-day window and flag functions over 15.
- Keep each refactor under 300 lines.
- Refactor code that produces regulatory or partner-reported figures only with a reconciliation test proving identical output.
See the Technical Debt Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.