I totally agree, but how then should we track requirements? How have people seen that work successfully? I have my ideas in theory, but all of my professional life has been in a world where user stories are the status quo.
“track requirements” does not make a lot of sense to me, but I will take a stab at, “How to set requirements without relying on user stories”:
Your statements in step 3 are requirements.
Your story does not exist (or can be whatever marketing/your manager/your spin doctor wants it to be), and how you go about satisfying those requirements is fair game to anyone that wants to do the work.
Sphinx Needs is the fancy new thing at my work. However, I’m in a regulated field so maybe something more lightweight is good enough for you already.
More important is to write them well (e.g. clear, testable, independent). I don’t know any tools for that though.