So on one hand it states:

Delivery is becoming a sequence of checks, not a ritual The same thing happens when it is time to deliver.

First, I invoke my /definition-of-done skill. It checks whether the implementation covers what was stated in the PR and in the plan. It checks tests and the other validations I care about. It tells me when something looks unusual, broken, or missing. When everything looks good, I invoke another skill, /pr-check-release. That checks the remote PR, updates labels, removes [WIP], adds [RFC], updates the description, and prepares the change for review. If one day passes and nobody on the team reviews the PR, we merge it. The agent also tracks that condition for me, so I can run /pr-merge-dev, and it takes care of the process: merge the PR, delete the remote branch, delete the local branch, and pull dev back into a fresh state. None of these steps is particularly difficult. That is exactly the point.

But then:

I still care about all of those things. Probably more than most people.

Obviously the author has irreversibly became AI-pilled and the day API costs balloon or APIs are down, what work will the author do?

I love using AI but please read the diffs and process them with your human brains and eyes. Spin up your containers manually, test the app, MANUALLY. Talk to real users face to face.

Outsourcing the grunt work is fine, but there's a fine line between that and becoming a button-presser.

> Obviously the author has irreversibly became AI-pilled and the day API costs balloon or APIs are down, what work will the author do?

I am old enough to remember having these thoughts when documentation for things moved from books to being online. I thought looking things up in the internet was a recipe for failure, because the internet was new and unstable and changing, and what happens if you run out of your 10 hours a month of being online, or if someone in your house picks up the phone and you are disconnected?

Clearly those people were internet pilled, and the day the internet costs ballooned or was down, what would they do?

I wrote software before Stack Overflow existed, before Git existed, and before most of the tools I use today existed. I think I will survive an API outage :)