ticket-generator

Generate Markdown engineering or product tickets from user inputs.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill ticket-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-generator
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/ticket-generator
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill ticket-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate well-structured engineering or product tickets from user inputs, turning vague ideas into explicit tickets with clear titles and descriptions.

Core Features & Use Cases

  • Accept a single input or multiple inputs (feature requests, bug reports, user stories, or requirements) and generate one or more tickets as needed.
  • Scan the codebase for context to pre-fill acceptance criteria and minimize clarifying questions.
  • Output each ticket in clean Markdown with a Title and Description, ready to paste into issue trackers.
  • Handle various contexts, including frontend, backend, bug fixes, and work-item breakdowns.

Quick Start

Provide a user input describing a feature or bug and let the skill generate Markdown tickets.

Frequently Asked Questions about ticket-generator

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

FAQPage Schema
How do I generate well-structured engineering tickets from vague feature requests?

To generate structured tickets from vague requests, provide your raw feature input and the tool will output clean Markdown with a Title and Description, scanning the codebase for context to pre-fill details.

Can I create multiple Markdown tickets from a single user story or bug report?

Yes, you can create multiple Markdown tickets from a single input. The generator accepts feature requests or bug reports and produces one or more structured tickets as needed for your workflow.

Does this ticket generator scan the codebase to fill in acceptance criteria?

Yes, the ticket generator scans the codebase for context to automatically pre-fill acceptance criteria, minimizing the need for manual clarifying questions before outputting the final Markdown.

What is the best way to turn raw requirements into clean Markdown for issue trackers?

The best way to turn raw requirements into clean Markdown is to input them directly; the tool processes the requirements and outputs structured tickets with Titles and Descriptions ready to paste into issue trackers.

Can I use this for breaking down work items across frontend and backend contexts?

You can use this to break down work items across frontend and backend contexts. It handles various development scenarios, including bug fixes and work-item breakdowns, generating appropriate Markdown tickets.