You already do
half of this.
Same skills, new hands
Look at what a business analyst does in a normal week. A to find the real question. A so the data lands in the right place. A for the developers. before anything goes live.
Now look at the from the last lesson: goal, spec, check, record. The developer's seat is taken by a , but every seat around it is one you already know how to sit in.
Sort your skills
Nine everyday BA skills, five places in the loop. Four places are yours. The fifth is the work the agent has taken over.
Predict first: which of your current skills transfers least to working with an agent?
Eight of nine skills land in a seat you keep. The one that moves becomes a check. You still need to know what a well-formatted card looks like. You just don't format 28 of them by hand.
What's actually new
Not everything carries over unchanged. Each skill needs one adjustment, and they share a cause: your reader is now an agent that never asks a follow-up question.
| Skill you have | Where it goes | The adjustment |
|---|---|---|
| Requirements workshop | Goal | End with a one-line goal in writing, not a shared feeling in the room. |
| Data mapping | Spec | Name the exact table, column and file, not the concept. |
| Functional spec | Spec | Every answer you'd give in a follow-up chat goes into the spec itself. |
| UAT | Check | Test what no automated check covers, such as what happens on a click. |
| Decision log | Record | keeps the log. You write the message and read the . |
Check: an agent asks no follow-up questions. What does that change about your spec?
The rule, in one breath
You're not starting over. You're moving up the loop: from doing the build to deciding, specifying and checking it.
The you wrote for developers are the ones the agent works to. The difference is that the agent takes them literally.
Next: from clicks to specs.