I've spent whole year aligning a team strategy with an overall company strategy, and making sure that rest of the people on my team build is actually fitting into that strategy.
In the past, team spend many years build custom stuff, that always had to be thrown away. Now, work we're doing is a part of a company direction, our expertise influenced it, and as a result we're no longer building throw away things, but also building something that impacts the whole company. I'll be blunt - I've made people on my team 10x more productive as a result.
At bigger companies there's many ways you can be a senior developer. Does it sucks that people need to do stuff like that? Oh yeah, I'd prefer to have 100s of CL this year. But that's often a motion, not progress. As a senior, I'm accountable to make sure we make progress.
But I don't think this is a particularly effective way to root those people out.
It's also possible he's reassigning teams from the ground up, and this is his sorting method.
"coordinate and plan technology" can be a huge amount of effort, vastly greater than "nothing".
Imagine if every hour of every work day in your calendar is full of various forms of "planning" meetings. How are you supposed to write code and attend all this nonsense at the same time? You can't.
To be fair it sure feels like doing nothing but employers consider it necessary and a job that only senior people can handle.
Another way to read this is as saying coordination and planning are the job. They "do nothing but", as in "only do".