automation-review
Installation
SKILL.md
automation-review
Core Philosophy
The most dangerous engineers are those who can automate anything in an afternoon, but never ask if it should be automated. Every automation is a permanent software maintenance liability: APIs break, dependencies rot, edge cases explode, and silent failures corrupt data. An automation review is a rigorous architectural and economic audit designed to evaluate value, failure modes, and long-term TCO—frequently concluding with the highest-leverage recommendation: "Do not build this."
4-Step Automation Audit Framework
Step 1: The Economic ROI & Break-Even Calculus
- The Core Automation Equation:
$$text{Annual Net Value} = (text{Hours Saved / Year} imes text{Blended Hourly Rate}) - (text{Initial Build Cost} + text{Annual Maintenance Cost})$$
- Build Cost: Engineering hours to build, test, and document $ imes$ Hourly rate.
- Annual Maintenance Cost: Historically 20–35% of the build cost per year (API migrations, bug fixes, edge cases).
- The "Rule of 50" Threshold:
- If a manual process takes $< 15$ minutes per week and is performed by 1 person, automating it is mathematically negative ROI unless error consequences are catastrophic.