It's more which subject to start with, as I can't learn all that at the same time.
Fair enough, let's see.
business, team management, basic programming, technical writing, art, both 3d and 2d, the unity engine(as that's most of what I'll be working with), and algebra/geometry
Do you have some kind of road map?
In other words, what can you postpone (since you seem to have too much now)?
In my limited view:
- "business" does not look interesting until you have a business, so after you got something that looks like it could become publishable?
- "team management" How many people do you expect to get in the near future. If it's a few or none, it sounds like it can be deferred for a while.
- "basic programming" (I am very biased here, take my advice with 2 grains of salt please.) sounds like a skill you need often. If you do programming yourself obviously, but even if you're more a designer, when it helps if you understand the world of the programmer.
- "technical writing" Not sure what it means, what do you expect to write in the near future? If it's requirements for a game design, my guess is that programming knowledge is at least useful here.
- "art" Definitely needed in the second part of the first game that you want to publish (and it has to be good then). Without programming no game though. If you want to do art for others, you don't have the programming requirement (although it's still useful for communication).
- "unity engine" I heard it has a nice scripting language for making a simple game. If that looks good to you (check out the tutorials), you may want to do "basic programming" in it, thus coupling unity with programming. Otherwise, you need to learn some (very) basic programming before using any engine.
- "algebra/geometry" Always useful. Edit: Maybe first make a few games that do not need this?
My ideas are just a random shot in the dark (and biased towards programming), but make a roadmap of your own (and do include lead time for learning, which I conveniently left out). If you don't know what you should do first, make both roadmaps, and compare.
I would suggest you don't do one thing at a time, but instead do them in parallel. Many of the subjects take years to master. If you do them together, you learn not only the skill itself, but also how to apply them in another skill.