I've created both plugins just to simplify/make the code more readable.
The routing plugin simply removes some boilerplate/makes the code easier to read.
I was building a simple email app just to see how wire works and this:
Instead of having a router spec which instantiated a module and connected the different modules I simply added this plugin to the main spec.
router:
bbRouter:
routes:
'': 'js/components/allemail/spec'
'archive': 'js/components/archive/spec'
'email/:id': 'js/components/singleemail/spec'
It works like a charm in 90% of the cases.
The extra plugin (bbconnect) was used to handle a situation where a route change had to update more than one module
bbConnect:
'route': 'viewModel.changeRoute'
simply allowed my nav bar to keep track of route changes.
I suspect that on really big applications you might need something slightly more robust, and the fact that you can't de-register a router in Backbone means you cant easily use subroutes (which I originally wanted to use)
But it's good enough for small/medium sized CRUD apps and I really don't want to write my own router at the moment :)