You can actually skip all the wire commands and still generate a valid netlist, however the schematic might be a bit hard to decipher if there are many components!
I did explore automated layout algorithms for components in the schematics, however the readability and flow of the schematics might not be ideal, depending on what the algorithm prioritizes.
In the end, I realized that the actual layout and arrangement of the schematic itself was critical in the overall understanding. That was when I decided to add the "wire" command and give more control back to the schematic designer.
In the future, I do plan to add some automated way to generate these "wire" commands for automated layout. If the designer ever chooses to edit this automated schematic layout, he would be able to edit the wire commands for finer control.
In the end, I do believe that the visual part of the schematic plays an important role in understanding it. I, too, have spent hours puzzling/being misled by poorly drawn/disorganized schematics. Especially during troubleshooting or creating an updated revision, having a good understanding of the schematic saves time.
One of the aims of Circuitscript is to make the visual part easier, so at least more time can be spent thinking and organizing the schematic itself.