Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+3)

Midnight Spire and Pritt have some great advice, especially in regards to tutorials. 

To add to that, I would recommend getting your basic game loop working before spending too much time with levels and assets. By "game loop" I mean all the logic from starting the game, playing a level and then failing or continuing to the next level, quit and restart options, etc. If you anticipate that your game will have a menu of some sort, do a very basic text-based menu first with only the most essential features (Start, Save, Load, Quit, etc).

Think of the "game loop" as the skeleton of the game. 

Thanks a lot! So just putting down the process that the player ideally would go through? Should I also run some play-testing to see if things work out for the player?

Basically, yeah. Have your initial "game loop" be a very basic player experience. Have two levels, one to play and test your game mechanics and then the next level is there to test that the game transitions to the second level properly if the first level is completed. Once your "game loop" is working, you can start to "flesh it out" with levels, sounds, music, assets, etc. 

I would also recommend archiving your project once you get the basic "game loop" done. This way, if you decide your game needs to be drastically different, you have a fully functional "skeleton" to work with so you're not starting from scratch.