Ticket Creation Skill

Create structured software tickets from brief problem descriptions.

Updated Dec 4, 2025

Search Tags:#automation #context #creation #ticket #acceptance-criteria #clarifying-questions #ticket-template

Ready to run

npx skills add https://github.com/HaywardMorihara/toolbox --skill ticket-creation-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Ticket Creation Skill
Source: https://github.com/HaywardMorihara/toolbox/tree/main/ai/skills/ticket
Command: npx skills add https://github.com/HaywardMorihara/toolbox --skill ticket-creation-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly draft clear, structured software tickets that capture context, constraints, and acceptance criteria, enabling engineers to own the solution without excessive direction.

Core Features & Use Cases

Structured ticket templates: Provide a consistent structure for problem, context, acceptance criteria, and open questions.
Context-first framing: Automatically surface relevant background and constraints to reduce back-and-forth.
Open questions & scope: Explicitly capture uncertainties to guide discussion and decision-making.
Acceptance criteria scaffolding: Include concrete, testable criteria to ensure a shared notion of done.

Quick Start

Provide a brief problem description and any available context, and ask the AI to generate a complete ticket structure following the template above.

Frequently Asked Questions about Ticket Creation Skill

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

FAQPage Schema

How do I create structured software tickets with clear acceptance criteria?▼

To create structured software tickets, provide a brief problem description to generate a complete outline including summary, context, user story, technical context, acceptance criteria, open questions, and testing considerations.

What should be included in a software ticket template for feature requests and bug reports?▼

A software ticket template should include context-first framing, structured problem descriptions, explicitly captured open questions for scope, and concrete testable acceptance criteria scaffolding to ensure a shared notion of done.

What is the best way to draft actionable software tickets that reduce engineer back-and-forth?▼

The best way to draft actionable software tickets is using context-first framing to automatically surface relevant background and constraints, explicitly capturing uncertainties to guide discussion and decision-making.

Can I generate a complete ticket structure from just a brief problem description?▼

Yes, you can generate a complete ticket structure from a brief problem description and any available context, producing a full outline that enables engineers to own the solution without excessive direction.

Does this ticket creation approach work for maintenance tasks as well as new features?▼

Yes, this ticket creation approach applies to bug reports, feature requests, and maintenance tasks, ensuring clear context, scope, and acceptance criteria across all software engineering ticket types.