It is not uncommon to find tasks nodes in a competency framework. In fact, in a "workforce framework", tasks are frequently the organizing mechanism for the framework; e.g.:
--Task
-----Knowledge
-----Skill
While tasks are defined in terms of a goal or objective--"Specific activity, typically related to performing a function or achieving a goal."-- the goal or objective should not be part of the task statement since doing so both limits the application of the task in other contexts than the one for which it was created, but it also tends to turn the task into a goal statement.
The NIST Knowledge Skill (TKS) Statements Authoring Guide for Workforce Frameworks states this explicitly:
[O]rganizational objectives should not be included in a Task statement in order to give organizations the flexibility to apply the task to meet their specific needs. In addition, if a Task statement includes an organizational objective, an organization may interpret that objective as the sole reason to conduct the task.
It is not uncommon to find tasks nodes in a competency framework. In fact, in a "workforce framework", tasks are frequently the organizing mechanism for the framework; e.g.:
--Task
-----Knowledge
-----Skill
While tasks are defined in terms of a goal or objective--"Specific activity, typically related to performing a function or achieving a goal."-- the goal or objective should not be part of the task statement since doing so both limits the application of the task in other contexts than the one for which it was created, but it also tends to turn the task into a goal statement.
The NIST Knowledge Skill (TKS) Statements Authoring Guide for Workforce Frameworks states this explicitly: