The reason we decided to use FB only auth is that we felt that in order to provide the same feature set with FB and without it would require quite a lot of duplication on our site. And the more social features we add - the more duplication it requires.
For example, for a plan you can specify "friends only" visibility - and for this to work we need to support friends lists in our app. We also use FB to send SMS reminders (if allowed by a user) - and that's not the easiest and cheapest thing to implement from scratch.
But I would probably offer a more basic version that doesn't have friend lists, SMS reminders, etc, and let the user opt in to the additional features only if they wanted to. Otherwise I think you might end up artificially restricting the amount/type of users that use your site (e.g. people without Facebook accounts or people that want to keep their Facebook data private).
I think relying on Facebook Connect only might be a bit iffy, unless you absolutely require it for core functionality. In your case, Facebook adds some social elements but the core competency of your website is building plans. I might want to sign up to play with your site without using my Facebook account. If I like it enough to recommend it to my friends, I might be willing to link it to my Facebook account later.