← Prompt Library / Engineering
Translate a technical debt problem into a business case a non-technical decision-maker can weigh: cost of inaction, options, and the ask.
Build the business case for fixing: {{debt}} (what's wrong technically, incidents/slowdowns it has caused, what fixing costs).
Translate for a non-technical decision-maker: the problem as a business risk (outages, slow delivery, security exposure — with the evidence from my notes), cost of inaction quantified where possible (hours lost/sprint, incident frequency trend), options — do nothing / patch / fix properly — each with cost and residual risk, the recommendation with a scoped ask (time, people, sequencing against feature work), and the measurable 'done' condition so this doesn't become an open-ended rewrite. No jargon; 'the database is tired' beats 'we have index fragmentation'.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...