ticket

Automate ticket lifecycle management with a CLI for creation, tracking, and migration.

Updated Mar 3, 2026

Search Tags:#automation #workflow #versioning #cli #ticket #plan-to-ticket

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ticket lifecycle management is complex and error-prone; this skill centralizes creation, tracking, handoff, resume, migration, and plan-to-ticket generation with consistent frontmatter and metadata.

Core Features & Use Cases

Atomic, frontmatter-based Tickets with Markdown bodies for automation and auditing.
Unified workflows for create, track, handoff, resume, migrate, and plan-to-ticket generation across versions.
Real-world scenario: quickly generate a batch of tickets with consistent structure and validation.

Quick Start

Install the CLI and run ticket track summary to view your current tickets.

Frequently Asked Questions about ticket

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

FAQPage Schema

How do I automate ticket lifecycle management for a software project?▼

Automated ticket lifecycle management is handled by applying unified workflows for creation, tracking, handoff, resume, and migration using a CLI and consistent frontmatter validation.

What is plan-to-ticket generation and how does it work with versioning?▼

Plan-to-ticket generation automatically converts project plans into structured tickets across versions, implementing validation and consistent metadata to ensure accurate end-to-end ticket generation.

Can I use Markdown and frontmatter for automated ticket tracking?▼

Yes, automated ticket tracking uses atomic, frontmatter-based tickets with Markdown bodies to support automation, auditing, and consistent metadata across the project lifecycle.

What is the best way to generate a batch of tickets with consistent structure?▼

The best way to generate a batch of tickets with consistent structure is by using the unified workflow CLI, which applies validation and frontmatter standardization across all generated tickets.

Do I need pyyaml to run the ticket CLI for workflow automation?▼

Yes, pyyaml is required as a dependency to run the CLI and support the workflow automation, validation, and frontmatter parsing needed for end-to-end ticket management.