ticket-track

Track versioned tickets with 5W1H fields and batch operations.

1|Updated Oct 17, 2025

Search Tags:#markdown #CLI #yaml #batch-operations #5W1H #versioned #ticket-tracking

Ready to run

npx skills add https://github.com/tarrragon/claude --skill ticket-track

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-track
Source: https://github.com/tarrragon/claude/tree/main/skills/ticket-track
Command: npx skills add https://github.com/tarrragon/claude --skill ticket-track

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ticket management in teams often suffers from scattered notes, inconsistent statuses, and manual coordination. This Skill provides a structured, versioned ticket-tracking system with clear 5W1H fields and batch operations to streamline progress across agents and phases.

Core Features & Use Cases

5W1H driven ticket design: capture who, what, when, where, why, and how across tickets; view relationships and task lineage.
Versioned progress tracking: each version has its own ticket set, status, and history to enable audit trails.
Batch operations: bulk claim, complete, and field updates to accelerate multi-ticket workflows.
Use Case: coordinate a multi-person feature rollout by tracking each ticket's status, owner, and log entries in a single place.

Quick Start

Initialize a version: uv run .claude/skills/ticket-track/scripts/ticket-tracker.py init v0.1.0
Add a ticket: uv run .claude/skills/ticket-track/scripts/ticket-tracker.py add --id T-001 --log v0.1.0-ticket-001.md --who "alice" --what "implement feature" --when "Phase 2 start" --where "src/" --why "feature requirement" --how "git"

Frequently Asked Questions about ticket-track

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

FAQPage Schema

How do I track structured ticket progress across multiple agents using YAML and Markdown?▼

Structured ticket tracking across multiple agents is managed through deterministic CLI commands that store data as YAML and Markdown files, enforcing 5W1H fields and versioned histories for coordinated progress updates.

Can I perform batch updates to claim or complete multiple tickets at once?▼

Batch updates for claiming and completing multiple tickets are supported natively. The system executes bulk operations through command-driven UPDATE actions, accelerating multi-ticket workflows across different project phases.

What's the best way to maintain an audit trail for versioned ticket workflows?▼

Maintaining an audit trail for versioned ticket workflows requires assigning each version its own dedicated ticket set, status, and history. This approach enforces deterministic tracking and preserves logs for chronological review.

Does this ticket tracking system work with Python and pyyaml dependencies?▼

The ticket tracking system works directly with Python and requires the pyyaml dependency to function. It operates through CLI scripts that parse and write YAML data structures to manage ticket states and relationships.

How do I query ticket relationships and task lineage using the 5W1H framework?▼

Querying ticket relationships and task lineage uses READ operations like tree views and 5W1H queries. This captures who, what, when, where, why, and how across tickets to clearly visualize task dependencies and historical connections.

When should I not use a CLI-based ticket tracking approach for team coordination?▼

A CLI-based ticket tracking approach is not ideal for teams requiring real-time visual dashboards or automated external notifications. It is designed for deterministic, command-driven workflows rather than continuous visual monitoring scenarios.