create-ticket

Generate standardized implementation tickets with frontmatter templates for .workaholic/tickets.

1|Updated Jan 15, 2026

Search Tags:#automation #metadata #ticket #frontmatter #software-engineering #workaholic

Ready to run

npx skills add https://github.com/qmu/workaholic --skill create-ticket-qmu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/create-ticket
Command: npx skills add https://github.com/qmu/workaholic --skill create-ticket-qmu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of structured implementation tickets by generating frontmatter and templates that align with your .workaholic/tickets conventions.

Core Features & Use Cases

Template-based ticket creation: Generate standardized frontmatter fields and a consistent ticket structure.
Guided workflow: Provides clear steps to capture metadata and format the ticket for archiving.
Use Case: When starting a new feature, run this skill to create a ready-to-use ticket with created_at, author, type, layer, and empty fields for effort, commit_hash, and category.

Quick Start

Run the create-ticket workflow to generate a new ticket skeleton in the .workaholic/tickets/ directory.

Frequently Asked Questions about create-ticket

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

FAQPage Schema

How do I create standardized implementation tickets with frontmatter in a software project?▼

To create standardized implementation tickets, this Skill automates the generation of metadata-ready ticket skeletons with proper frontmatter templates in the .workaholic/tickets directory. It ensures required fields like created_at, author, type, and layer are properly formatted for archiving.

What is an in-repo ticket workflow and when do I need frontmatter metadata?▼

An in-repo ticket workflow stores implementation tickets directly within the project repository. You need frontmatter metadata when your pipeline requires structured fields like created_at, author, type, and layer to automatically parse, track, and archive tickets across branches.

How do I generate a ticket template for the .workaholic/tickets directory?▼

You generate a ticket template by running the create-ticket workflow, which produces a ready-to-use ticket skeleton in the .workaholic/tickets directory. This skeleton includes populated metadata fields and empty fields for effort, commit_hash, and category.

Does this automated ticket creation work across different Git branches?▼

Yes, automated ticket creation works across branches by generating standardized tickets within the .workaholic/tickets directory. This ensures consistent metadata formatting regardless of the branch you are currently working on.

What frontmatter fields are required for archiving tickets in a ticketing pipeline?▼

Required frontmatter fields for archiving tickets include created_at, author, type, and layer. The Skill also generates empty fields for effort, commit_hash, and category to be populated later during the implementation process.