ticket-manager

Ticket management automation organizes and tracks work items through their lifecycle. This Skill creates, updates, and searches tickets with structured fields like status, priority, and assignee, eliminating manual file tracking and ensuring consistent project data across backlog, todo, in_progress, review, and done states.

Yes. This Skill manages tickets stored locally in JSON format with built-in filtering by status, priority, assignee, and sprint. Tickets are automatically assigned unique IDs (TICK-XXX) and tracked with created/updated timestamps, giving you full control over work organization without external dependencies.

Create multiple tickets at once with structured data including title, description, status, priority, and assignee fields. The Skill generates consistent ticket IDs and timestamps automatically, letting you bulk-populate sprints with properly organized work items ready for team assignment.

Ticket tracking supports filtering and search across status, priority, assignee, and sprint fields. A Grep-based search option enables flexible text matching, allowing you to locate tickets by any combination of these attributes or custom keywords within ticket content.

No. This Skill uses a file-based JSON store (.claude/data/tickets/) for all ticket records, requiring no external databases or project management platforms. It handles complete CRUD operations locally, making it lightweight for teams managing tickets within their development environment.

Updates preserve ticket history with automatic updated timestamps while maintaining the original created date and ticket ID. Status changes move tickets through your workflow states, and all modifications are persisted to the local JSON store, keeping your project state current and auditable.