rspec

I would like to rewrite the parser for stories to meet the following goals:

1) Allow new phrase types to be added by projects outside the rspec source tree.

2) Allow defining any step with a scenario like construct so stories can be decomposed into stories to several levels of depth before dropping into ruby.

3) Allow more flexibility in matching step specs to steps and sscenario like decompositions. In particular making it easier to have several steps that have similar syntax in matching. This may require allowing more flexible matching syntax than the current simple regular expression use.

The reason for this request is to make stories a language that can be used for full system specifications in business owner readable language, with executable semantics under the covers. The current system while a big step forward is still too techy for many business owners unless the ruby side has a one-to-one matching to the english step descriptions. It would also be useful to allow story decomposition so chunks of system function can be described in stories and still reused in larger sequences.