tracking-system

Manages file-based tickets, comments, links, and workflow transitions through a Python CLI.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/t-jet/pal_found_cli --skill tracking-system-t-jet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracking-system
Source: https://github.com/t-jet/pal_found_cli/tree/main/.ept/skills/tracking-system
Command: npx skills add https://github.com/t-jet/pal_found_cli --skill tracking-system-t-jet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes references (resource) components.

What problem does it solve? Coordinating multi-agent or multi-role work requires a consistent ticket tracker, but ad-hoc file edits corrupt state and bypass workflow rules. This Skill provides a governed CLI for creating, updating, linking, and querying tickets with validated status transitions and automatic transition rules. ## Core Features & Use Cases - Ticket Lifecycle Management: Create, read, update, list, and search tickets of configurable types (task, feature, bug, epic, question, and more) with validated statuses, priorities, and fields. - Comments and Inter-Ticket Links: Record decisions as comments and model relationships such as blocking or containment with auditable link records. - Workflow Inspection and Build Queue: Query ticket type definitions, allowed transitions, and definitions of done, then generate a prioritized build queue with blocking relationships and priority reconciliation. - Use Case: An AI agent picks up work by running build-queue all to get the prioritized queue, checks workflow transitions before moving a ticket to In Progress, and logs its plan as a ticket comment. ## Quick Start Ask the agent to list all non-terminal tickets assigned to a role using the tracking-system CLI, then create a new task ticket with a title, priority, and author.

Frequently Asked Questions about tracking-system

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

FAQPage Schema
How do I create and update tickets from the command line?

Run tracker_cli.py create with a ticket type, title, and required --author flag, then use update with the ticket ID to change status, assignee, priority, or fields. Status changes are validated against allowed_transitions in the workflow configuration.

How do I generate a prioritized build queue of tickets?

Run tracker_cli.py build-queue all to filter non-terminal tickets, reconcile priorities across parent-child and blocking links, sort by priority, and print the queue with blocking relationships. Individual stages can be run via stage1 through stage4.

What dependencies does the tracking CLI require?

The CLI requires Python 3.11 or later and PyYAML 6.0 or later, as declared in pyproject.toml. It must be run from a project where the .ept/tracker/ configuration directory exists.

Why does a ticket status update fail with a validation error?

Status updates are rejected when the target status is not in the allowed_transitions map for the ticket type and current status. Run workflow transitions <type> <current-status> first to see which moves are permitted, then retry with a valid target.

Can I edit tracker files directly instead of using the CLI?

No. Direct reads or writes of .ept/tracker/ storage, indexes, and workflow files are prohibited because the internal layout is not part of the agent contract. All operations must go through the documented CLI commands.