taskwarrior-issue-tracking

Manage issues offline with Taskwarrior v3 CLI commands.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/peter-jerry-ye/skills --skill taskwarrior-issue-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskwarrior-issue-tracking
Source: https://github.com/peter-jerry-ye/skills/tree/main/skills/taskwarrior-issue-tracking
Command: npx skills add https://github.com/peter-jerry-ye/skills --skill taskwarrior-issue-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to manage issues locally using Taskwarrior v3 as a CLI issue tracker, providing an offline, lightweight alternative to Git-based workflows.

Core Features & Use Cases

  • Offline issue tracking: Represent issues as Taskwarrior tasks with project/tag metadata and explicit status transitions.
  • Triage and ownership: Claim tasks with agent tags and plan work using dependencies to block progress.
  • End-to-end workflow: Create, update, and close tasks, annotate progress, and ensure a cohesive session completion.

Quick Start

Identify the current project and list tasks: task project:repo:github.com/peter-jerry-ye/skills Pick a task and claim: task <id> modify +agent-codex Plan the work before execution: Create dependency tasks and link with depends:<id-step1>, depends:<id-step2> to model steps Complete the task: task <id> done Follow-ups: task add project:repo:<host>/<owner>/<repo> +ready "Follow-up: <short title>"

Frequently Asked Questions about taskwarrior-issue-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage issue tracking offline without relying on Git integration?

You can manage issue tracking offline by using Taskwarrior v3 as a local CLI tracker. It allows you to create, triage, update, and complete tasks locally using project naming schemes and dependency-based planning without needing Git.

Can I claim and assign tasks to specific agents using Taskwarrior?

Yes, you can claim tasks for triage and ownership by applying agent tags. Use the command `task <id> modify +agent-codex` to tag tasks, ensuring clear ownership during your local workflow execution.

How do I plan task dependencies before starting execution in a CLI issue tracker?

Plan work before execution by creating dependency tasks and linking them. Use the `depends:<id-step1>` command to model steps, which blocks progress on subsequent tasks until prerequisites are completed.

What is the best way to annotate progress and close completed tasks in Taskwarrior?

The best way to annotate progress is to use explicit Taskwarrior commands during status transitions. Once finished, close completed tasks by running `task <id> done` to ensure a cohesive session completion.

Does offline issue tracking support reproducible workflows for team environments?

Yes, offline issue tracking enforces a reproducible workflow using a project naming scheme, dependency-based planning, owner tagging, and explicit progress annotations, ensuring consistent task management for teams locally.

How do I add follow-up tasks to an existing local project repository?

Add follow-up tasks by executing `task add project:repo:<host>/<owner>/<repo> +ready "Follow-up: <short title>"`. This maintains your project structure and ensures the new task is ready for triage.