I guess user stories in their raw form don't really even necessarily help with this, since there's no reason I can't just do:

As a project manager, I want view a Gantt chart of all tasks in a project.

...which puts us back at square one.

As a <role>, I want <goal/desire> so that <benefit>

I don't have any specific short-term plan. It could be part of Nuance or something?

Ask Question -> Ponder
Report Bug -> Maniphest
Request Feature -> Nuance

It still seems pretty easy to not actually describe the problem you're facing when filling out that kind of template:

As a designer, I want all files mentioned on a task to be listed in the header so I can quickly find them.

A template more like:

As a <user>, I encounter <problem> when I try to <goal>. [One way to improve this might be <solution>.]

...might help, but I can still do something like this easily:

As a designer, it takes a long time when I try to find files that were mentioned on a task. One way to improve this might be to list them in the header.

I wonder if we'd have better luck with just:

What problem are you encountering? Describe your problem, not your desired solution.
[ big text field ]
(Optional) If you have a solution in mind, describe it here.
[ big text field ]

Anyway, something we can play around with at some point.

It still holds some reasonable interest to me for a feature (overall in Phabricator). We are generally experienced ourselves at defining and building product, as are at least some of our users, but this isn't the norm in all of software. It would be likely more useful to customers who have consumer facing products and users who are not as savvy, in a somewhat common manner. "User Stories" were gaining popularity at Facebook in the User Researcher roles, and I did find they provided some value at getting quickly to a core issue. I also see stories in many "agile" products and am honestly curious how they'd affect our feature management. If we had Nuance, it seems a quick test to just wire up a form on Phacility and pump the info there.

I think a critical feature of Nuance is being able to create "contact forms" -- like a form to submit a user story -- and then these forms should be iterated on as necessary to improve the signal to noise ratio. Probably not V1 but definitely V2 type stuff in my opinion.

This request is too specific since different organizations might need different things. However, what about offering a configuration option to pre-populate Maniphest tasks with a template?

In T6836#89146, @chad wrote:

Report Bug -> Maniphest
Request Feature -> Nuance

Let me just say that one of the beauties of Maniphest is that allows to handle bugs and feature requests and just any other potential or actual task in the same place. Projects/tags provide all what you need to categorize items.

You can already template some things with url parameters. For example /maniphest/task/create/?projects=foo. I'm not sure that's documented anywhere or which php file to pull the full list of possibilities from.

See T3320 for prefilling.