I think the article is too negative. User stories aren't a magical silver bullet that's going to fix all your problems, but having a good way to write down what

I think the article is too negative. User stories aren't a magical silver bullet that's going to fix all your problems, but having a good way to write down what the user wants, and forces them to think about it in a structured way, is really helpful. I'm sure everybody here has seen poorly described tickets that don't really make clear what the intention is. Of course "as a $role I want $feature so I can $purpose" is still pretty brief, and I've seen far more detailed templates, but it's good to have something at least. And yes, these stories don't remove the need for more comprehensive requirements and design. They're good for the additions to that, but shouldn't replace them entirely.