The code already assumes a method is a workflow method if it starts with ```wf_```. I think we should either:

1. Keep this assumption in place and remove ```@no_requirements```. Leave ```@priority``` optional. OR:
2. Remove the ```wf_``` prefix assumption and require that users either tag the method with something like ```@workflow_method```, give it an ```@requires```, or ```@priority``` (any of these tags would be sufficient to determine that a method is a workflow method I think).

I like the latter because it allows devs to be less restricted when naming methods, and IMO it is more explicit to have a method tagged with ```@workflow_method``` than using an implicit ```wf_``` naming rule.