Thinking a bit on step 5. Even if you developed the package during a larger project. Wouldn’t it be better to move it to a specific laravel project meant for package developement and then include it via composer as usual.
First of all it will probably help keeping project specific stuff out of the package, second there is no chance of pushing project stuff (that may or may not be private) to the public github repository.
Just a thought… ;) Very nice article, will look forward to try my own attempt at a package following this.