I am not sure whether anything similar already exists, but i dont think it would be tough to
implement.
One of the approaches would be to store the features in a table - the features can be associated
with functions or in the function(as mentioned in the same ruby code there, in this case-the view)
check the value of this feature and have the flow based on this.
(So, if you notice, its basically a lookup)
-V
http://twitter.com/venkasub