The agent ecosystem course
  • 0Before you start
  • 1Claude Code
  • 2The mental model
  • 3Map your ecosystem
  • 4The brief
  • 5The connectors
  • 6The runbooks
  • 7Working hours
  • 8The ecosystem
  • 9The backup
  • 10Sharing skills
  • 11Getting found

The stages

  • 0Before you start
  • 1Claude Code
  • 2The mental model
  • 3Map your ecosystem
  • 4The brief
  • 5The connectors
  • 6The runbooks
    • 6.01The runbooks, how you do each job
    • 6.02Where they live
    • 6.03Skill or brief, which goes where
    • 6.04How it finds the right one
    • 6.05An example skill
    • 6.06Which jobs to hand over, the five questions
    • 6.07Write your first one, by interview
    • 6.08Test it before you trust it
    • 6.09Ready when, what goes wrong, and homework
    • 6.10[BONUS]One skill handing to another
    • 6.11[BONUS]The LLM Council, five advisors on one decision
    • 6.12[BONUS]The runbook that improves itself
    • 6.13[BONUS]A skill that plays your client
    • 6.14[BONUS]A deeper version, not a bigger one
  • 7Working hours
  • 8The ecosystem
  • 9The backup
  • 10Sharing skills
  • 11Getting found
BACK TO THE COURSE

Stage six, session two

The runbooks

It knows who it is and it can reach your things. Now it needs to know how the repetitive jobs are done here, written down once as a skill.

6.06

Which jobs to hand over, the five questions

Not every job should be handed over, and here is a way of thinking about which.

You have been deciding what to delegate for as long as you have worked with people, and the same five questions apply here, each scored zero, one or two, where two means hand it over.

The question

A morning briefing

A summary of new regulation, to a client

1Is it even worth it?

2

The briefing

every morning, and it drags

0

The regulation

only when the rules change

2Could you teach it to someone in ten minutes?

2

The briefing

you can say exactly what goes in it

0

The regulation

you cannot, because it is new

3Can you check it?

2

The briefing

you would spot a wrong one in seconds

0

The regulation

only by reading the regulation yourself

4If it is wrong and nobody notices, where does it end up?

2

The briefing

nowhere, nobody else sees it

0

The regulation

with a client, with your name on it

5Are you the reason it is any good?

2

The briefing

anyone competent could write it

0

The regulation

it is good because it is you

Out of ten

10hand it overA morning briefing

0keep itA summary of new regulation, to a client

Where a job scores badly, nothing about that is a failure of AI, it is the wrong shape for handing over, and it would have been for a new starter too.

The one that catches people out is can you check it.

If you have to redo the work to know it is right, the job has not been done, it has come back to you as proofreading.

Most of your work lands in the middle, where you keep the judgement and it does a defined piece.

Then set up one, not all of them.

The prompt below has the agent interview you about a normal working week, score every job in it, and hand you the list highest first.

Argue with two or three of the scores before you believe it, and take comfort that some of the jobs on it are staying yours.

Score your week
I want to work out which parts of my job are worth handing over to you, and which I should keep doing myself. First, interview me. Ask me about a normal working week, one question at a time, until you have a list of the jobs I do regularly. Do not guess or fill the gaps in for me, and keep going until you have at least eight. Then score every job on these five questions, zero to two on each, where zero is not likely at all and two is very likely, and two always means hand it over: 1. Is it worth it. How often does it happen, and how long does it take? Two for weekly and painful, zero for twice a year and ten minutes. 2. Can I teach it. Could I show someone the whole thing in a ten-minute screen share? If it only exists in my head, it is a zero until I write it down. 3. Can I check it. How long does verifying the output take against just doing the job myself? Two for a glance, zero if I have to redo the work to know whether it is right. 4. What if it is wrong and nobody notices. Two for an internal draft, zero for anything going to a client, a regulator or my accounts. 5. Am I the reason it is any good. Two if a competent stranger would produce much the same thing, zero if the value is my judgement or my name on it. Give me a table of every job with its five scores and its total out of ten, sorted highest first. Split them into three groups, eight to ten is hand it over, four to seven is split it, zero to three is keep it. Where you had to make a judgement call on a score, say so and tell me what you assumed, so I can correct you. Finish by naming the single job I should hand over first, and telling me exactly how you would set it up.

Whatever comes out top, the one you build next is the inbox job you have already been doing by hand, because you know what good looks like on it.

The agent ecosystem course

Which jobs to hand over, the five questions

This is part 6.06 of the course. Start it free and it opens straight away, with no password.

A few quick questions come next. You will also get my Thursday newsletter, and you can unsubscribe from it without losing the course. How your details are kept is in the privacy policy.

Already have access? .