Indeed the term in software development would be "technical lead" or "architect", maybe "technical architect" if the project has more variety and has differently flavored architects. As titles are not regulated, it might be anything close to those.
I found it's not as much a soft skills role as management. In management you need soft skills to sell your people stuff they don't really want to do. As a technical architect it's way easier because you need to sell things they should want to do. Your suggestions should make their work easier if you are doing your job right and that's not hard to sell.
So yes, it sure helps to read some books about people and project management, just to know what you miss out on. Just to know what the others act upon.
Personally, I like Peopleware a lot, although it's quite old already.
What is more important is your technical knowledge. Your programmers will respect you on the base of your technical knowledge. So you need to keep that up to date. Even on technologies you don't use, because you should know why you don't use that technology instead.
I guess I don't need to tell you what to do in that regard. Books, Conferences, User groups, hobby projects.
One important aspect is that the more you get into a supporting role of teaching and planning, the more you lose contact with the people doing the real work. Once in a while, drop all your books and plans and cancel your meetings and get your boots dirty. Grab a ticket and implement it. That's important because you will experience the problems first hand and make better decisions for your programmers that way. I have seen too many ivory tower architects, that insist on doing it one way while the compiler insist that it's wrong. Keep your contact to the roots and know what you are talking about in detail. If your people see that you can do what they have to do, it's a lot easier to convince them to do it also. If your solution has 100% code coverage and works great, it's easy to sell. If your solution is 5 years old and unmaintainable crap, people will have a hard time respecting your guidance. Practice what you preach.
So in short:
- if you feel challenged to sell your ideas to the developers, get technical help. Courses, Books, Conferences.
- if you feel challenged to sell your ideas to management, get help with your soft skills. Courses, Books, Coaching.
There is no official path into that job or advancing in it. You will need to find your balance between those two.