Oftentimes when I'm writing a new recipe, I'd like to re-run that task, and only that task. I don't want the dependencies to run because they might take a long time, and I know they're up-to-date.

Another way to say this is: I'd like a way to run the recipes specified explicitly given on the command line, without any dependencies. One example I can find of this feature is Fake's --single-target parameter.

I'm aware of several workarounds for this, but it would be very nice to have this feature baked in. To list a few of the workarounds, so that I might illustrate why I would like this feature:

1. Write the dependencies with something like entr so that they don't unnecessarily re-run, as suggested in Tracking Incremental Changes (Avoid re-running builds) #424. This requires me to focus on having very robust dependencies before focusing on the task that I'm actually trying to work on. Sometimes I'd rather write the whole tree quickly and then go back and add such niceties.
2. Split each of my recipes into two. One which is my recipe, containing no dependencies. The second recipe includes the dependencies and includes the first recipe as the final dependency. This makes the justfile much less readable, though. Not great to maintain.
3. Comment out the dependencies as I'm developing the task. This works until I forget to uncomment them when I'm done.