task

We split this skill into the rules it gives an agent

9 rules. 0 are common, 0 are distinctive, and 9 are very specific to this project.

• 0

  Common

  Most of the 24 edited versions we read keep these.

• 0

  Distinctive

  This author's own choices. Worth a look.

• 9

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Create: Use create_task — needs title, optional assignee and priority

   line 9
2. Very specific:

   List: Use list_tasks or get_my_tasks — show pending work

   line 10
3. Very specific:

   Overview: Use get_task_overview — summary of all tasks by status

   line 11
4. Very specific:

   Update: Use update_task — change title, description, priority

   line 12
5. Very specific:

   Move: Use move_task — change status (todo, in_progress, done)

   line 13
6. Very specific:

   Complete: Use complete_task — mark as done

   line 14
7. Very specific:

   Assign: Use assign_task — delegate to a team member

   line 15
8. Very specific:

   Delete: Use delete_task — remove a task

   line 16
9. Very specific:

   If the user just says "tasks" with no context, show their task overview with get_task_overview.

   line 18

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.