create-ticket

Automates ticket creation with templates and knowledge references for software teams.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sato-dev1234/claude-code-sample --skill create-ticket-sato-dev1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/sato-dev1234/claude-code-sample/tree/main/skills/create-ticket
Command: npx skills add https://github.com/sato-dev1234/claude-code-sample --skill create-ticket-sato-dev1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of standardized tickets by combining templates with curated knowledge references, eliminating manual drafting and ensuring consistency.

Core Features & Use Cases

  • Auto-generates ticket IDs and applies templates from the knowledge refs.
  • Ensures consistency by injecting knowledge refs into the ticket draft for rapid validation and alignment with standards.
  • Use Case: When starting a new feature or bug fix, generate a ticket skeleton with AC items and references.

Quick Start

Create a new ticket by triggering the create-ticket workflow with required inputs such as the ticket title and scope.

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I automate ticket creation with templates for project planning?

Automating ticket creation with templates applies standardized structures and knowledge references to generate consistent ticket skeletons for project planning, eliminating manual drafting and ensuring rapid validation across software teams.

What is the best way to generate standardized tickets with auto-generated IDs?

Generating standardized tickets is best handled by triggering an automated workflow that auto-generates ticket IDs and injects knowledge references into a template, ensuring validation and alignment with project standards.

How do I create a ticket skeleton with acceptance criteria and references for a bug fix?

To create a ticket skeleton for a bug fix, trigger the ticket creation workflow with required inputs like the ticket title and scope, which applies templates to automatically generate acceptance criteria items and relevant knowledge references.

Can I use automated ticket templates for requirement gathering and documentation tasks?

Automated ticket templates can be used for requirement gathering and documentation tasks across software teams, applying curated knowledge references to ensure standardized output and rapid alignment with project requirements.

Why does my ticket drafting process lack consistency across new features?

Ticket drafting lacks consistency when manual processes are used, but injecting knowledge references into automated template workflows ensures standardized ticket output and alignment with project validation standards.