- Industry
- Retail
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-10
It finds the code in the storefront, commerce services and store systems that costs the most in incidents, slow changes and peak trading risk, and decides which debt to pay down this quarter. It proposes refactors ranked by cost avoided and fits them around the trading calendar.
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 issue tracker: incidents, bug counts and change lead times by service, and the debt register..
- 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 Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it creates the approved refactor tickets with their quarter and owner. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The technical debt register: known debt items, their incident and change cost, the services with peak trading risk, the end-of-support dates for platforms and the refactoring guidelines.
Reads from
the issue tracker: incidents, bug counts and change lead times by service, and the debt register.
Acts in
the issue tracker: it creates the approved refactor tickets with their quarter and owner.
Hands back
An object with items (a list of item, service, annual_cost, effort_days, rank and decision do_now, schedule or accept), capacity_used_days and reasoning.
Asks a person when
The plan takes more than 20 percent of capacity, or rewrites a checkout, till or order service.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Share of capacity for debt (%) | 20 | The share of engineering time debt work may take. |
| Cost of an incident hour (USD) | 15000 | Used to cost debt by the incidents it causes. |
| Weight for peak trading risk | 2 | Debt in services critical at peak trading is weighted by this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Cost each item by incident hours times 15000, plus slower change time, weighted by 2 for services critical at peak.
- Fit the plan within 20 percent of capacity.
- Platforms reaching end of support within a year go first.
- No refactor lands in the peak trading freeze; schedule them before or after.
- Every refactor ships with tests that pin current behaviour first.
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.