What would be the project description, and how would it be supposed to be used?

@Aklapper: As part of yearly planning, the Release-Engineering-Team has each team member formulate personal goals for the year. I think other WMF teams do this as well? At any rate I would like to track them in phabricator instead of keeping an unstructured list in some document somewhere else.

...adding a description to this task's description

In T138451#2405421, @mmodell wrote:

@Aklapper: As part of yearly planning, the Release-Engineering-Team has each team member formulate personal goals for the year. I think other WMF teams do this as well? At any rate I would like to track them in phabricator instead of keeping an unstructured list in some document somewhere else.

...adding a description to this task's description

it might also get randomly applied as well.
Isn't that more of a #User-BLAH type tag. #personal-goal just indicates that somewhere, someone has this a goal or something. I imagine a subproject or column on the rel-eng-team workboard would also be wanted.

I'm aware of other WMF teams also having personal goals so it is more common.
I'm wondering how much someone would actually query for tasks in both the projects #Personal-Goal × #some-team?

Although I am generally in favour of various tagging for the sake of better order and increase of reusability of the data in Phabricator, I am quite hesitant in this particular case because of being afraid of the exact opposite partially already mentioned by @Peachey88 earlier. I can easily imagine often misuse by tagging pretty much any assigned task because in fact it then becomes a sort of "personal goal".

Assuming (based on T131915: Technical Collaboration quarterly goals for July - September 2016) that these personal goals are for some given time-frame. So instead I would suggest to create Goal tagged task named eg. like "<team name> <time frame> personal goals" with having these personal goal tasks as its subtasks.