When I said "Usually if you are suggesting a plugin or behavior, it helps to give a comprehensive description and possibly an example list of the actions, conditions and expressions it might feature", I didn't mean paste in the actions, conditions and expressions of an existing behavior. That's not thinking through how it's going to work at all! Rather than focus on the similarities to another behavior, focus on the differences, what's new about it, what it will do, how it will do it, why it's easier, why it's better than existing ways, how it integrates with existing features, the ways in which it will control objects, etc. etc. etc. There's a lot to think about.
Behaviors aren't made by waving a hand and saying "it'll probably do something like that". Behaviors like the RTS movement are extremely carefully thought out and the algorithms and functionality are very carefully designed. That's necessary because programming is necessarily specific (you're instructing the computer precisely what to do). Feature requests which aren't well thought out are vague (so programmers don't see the benefit of going to all the effort) and also may result in something you didn't want, because you never said exactly what it was you wanted!