Take one thing you redo every week and turn it into a file that runs it for you — written, tested and handed to your team in an afternoon.
There is a task you do every week that you have never managed to give away.
The Monday numbers. The client update after a call. The list of who has not paid. It takes forty minutes, it is not hard, and it is somehow still yours in the second year. You have tried delegating it twice. Both times the output came back wrong in a way you could feel but not explain, so you took it back.
That task is not a delegation problem. It is a writing problem. Nobody ever wrote down what you actually do — the inputs you pull, the three judgement calls you make without noticing, the shape the finished thing has to have. It lives in your hands, not on paper, and you cannot hand over your hands.
A skill is that description, written down properly, in a file. Once it exists, a model runs it, a new hire runs it, and you check the output instead of producing it. This guide walks the whole loop on one real process: choosing it, extracting what you do, writing the file, testing it against a week you have already lived, and handing it to someone else.
You will finish with one working skill, not a plan to write one. Budget an afternoon.