podikoglou/taskwarrior-skill

Overview

This skill manages tasks through the Taskwarrior CLI with strict enforcement of project, tag, and lifecycle rules. It ensures every task is attributed correctly, trackable, and follows a consistent start/work/done flow. The agent always tags created tasks with +agent to preserve provenance.

How this skill works

The skill interacts with Taskwarrior commands (task, add, start, done, mod, queries) and validates operations against a rule set before acting. It enforces that each task belongs to a project and has at least one tag, requires marking tasks as in progress before work, and marks them done after completion. Agent-created tasks are automatically given the +agent tag and dependencies must be specified explicitly when modified.

When to use it

• When you need strict, auditable task creation and updates using Taskwarrior
• To keep every task associated with a project and at least one tag
• When an agent will create or modify tasks and you must record agent provenance (+agent)
• To enforce a consistent workflow: start before working, done after finishing
• When managing dependencies and project-scoped task lists

Best practices

• Always include project:PROJECT on task creation to satisfy the mandatory project rule
• Add at least one descriptive tag on every task; agent-created tasks must also include +agent
• Mark a task with task start ID before beginning work to reflect in-progress status
• When finished, run task done ID to close tasks and keep lifecycle clean
• When modifying dependencies, re-specify the full depends: list — Taskwarrior does not append automatically

Example use cases

• Add a future work item in project foo with a required tag: task add project:foo +planning +agent Prepare roadmap
• Start work on an assigned task: task start 12 to set it in progress before doing work
• Create a task that depends on others: task add project:ops +deploy depends:3,4 Run deployment checklist +agent
• Change a task’s project or tags: task 7 mod project:infra +urgent to move and reclassify it
• Close completed work items consistently: task done 7 to mark the lifecycle end