I am not saying this is a bad approach or concept. It is just that every programming language, every framework, every methodology/philosophy feels it needs to come up with its own sets of special concepts/buzzwords and naming conventions...
This has some truth to it, but agile vs. traditional development are one of the few circumstances where it makes sense to use different words because they are actually different things, not just different labels.
A story isn't really the same as a task - as mentioned above task means it's own thing. A story is more like a feature or function written from the user's point of view.
I do think the use of "epic" is too cute for my taste, but I guess "anthology" wouldn't be much better