taskery

The Taskery Full Operator skill provides a structured instruction set designed to empower AI coding agents with the capability to manage tasks within a Taskery environment. Taskery is a local-first Kanban system that synchronizes a web-based board with CLI and API interfaces, making it an ideal tool for developers who use AI agents to automate project workflows. By utilizing this skill, an agent learns to interact with the Taskery SQLite database via local terminal commands or RESTful API endpoints while respecting the optimistic concurrency model required to prevent data collisions.

This skill is intended for AI agents operating in local development environments where they need to transition from code generation to project management, such as creating tracking tickets, moving tasks through status columns, or flagging dependencies. It covers the full lifecycle of task management, from initial creation to final deletion, ensuring that agents can effectively collaborate with human team members using the same board.

• Full lifecycle management: create, inspect, update, move, review, complete, and delete tasks.

• CLI proficiency: deep integration with commands like list, show, create, update, and move, including usage of filters for status, priority, and assignees.

• API capability: interaction with REST endpoints including task management, system health checks, and global notification settings.

• Optimistic concurrency: strict adherence to versioning requirements via expectedVersion to prevent race conditions during concurrent updates by multiple agents or users.

• Workflow automation: guides agents on how to use exit codes (0–4) for robust error handling and automated retries when version conflicts occur.

• Environment versatility: supports both default local run-modes and custom API base URL configurations for flexible deployment.

• Always run 'show <id>' before performing mutation operations to retrieve the current task version.

• Use JSON-first output from the CLI to ensure machine-readability during task parsing.

• Statuses include PENDING, STARTED, BLOCKED, REVIEW, and COMPLETE.

• Priorities range from LOW to URGENT, aiding in effective backlog triage.

• Re-fetch and retry exactly once if a VERSION_CONFLICT (exit code 4) is encountered.

• Validate state after every write operation by invoking the list command to ensure consistency across the Kanban board.