Looking at the original request, the intention was to instruct the developer that calling a class some:weird:name is not valid from a console input validation point. At the moment PhpSpec ignores PSR rules and tries to create some:weird:name.php and a class with that name, resulting in a PHP Parse error, which breaks the PhpSpec flow. In my opinion the describe command should validate the pattern and display a common symfony console exception message