ticket-creator

Create structured GitHub issues from raw feature ideas via gh CLI.

Updated Nov 8, 2022
One-click install
npx skills add https://github.com/gvinokur/qatar-prode --skill ticket-creator-gvinokur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-creator
Source: https://github.com/gvinokur/qatar-prode/tree/main/.gemini/skills/ticket-creator
Command: npx skills add https://github.com/gvinokur/qatar-prode --skill ticket-creator-gvinokur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many feature ideas and problem reports arrive as vague requests or implementation-level notes that are not ready to become actionable GitHub issues; this skill guides a short interactive process to turn those raw ideas into well-scoped, user-focused tickets suitable for triage and planning.

Core Features & Use Cases

  • Interactive Clarification: Ask targeted, minimal follow-up questions to capture the user's intent, primary user, and any existing behavior being replaced or extended.
  • Feature-level Enforcement: Ensure tickets describe user-facing behavior only and strip implementation details from the issue body.
  • Issue Creation Workflow: Format the issue with Objective, Problem/Background, Acceptance Criteria, Out of Scope, and Open Questions, then create the GitHub issue via the gh CLI and set project fields for Priority, Effort, and Category.
  • Use Case: Product discovery or ad-hoc brainstorming when a PM or stakeholder says "let's create a ticket" and a clear, testable story is needed.

Quick Start

Draft a new user-facing ticket describing that leaderboard entries show rank changes, clarify acceptance criteria and out-of-scope items, and create a GitHub issue labeled story with medium priority and M effort.

Frequently Asked Questions about ticket-creator

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

FAQPage Schema
How do I create structured GitHub issues from raw feature ideas?

To create structured GitHub issues from raw feature ideas, this skill interactively asks targeted questions to clarify intent, formats the ticket with Objective, Acceptance Criteria, and Out of Scope sections, then creates the issue via the gh CLI.

What is the best way to write user-focused acceptance criteria for GitHub tickets?

Writing user-focused acceptance criteria involves enforcing feature-level wording and stripping implementation details from the issue body. This ensures the ticket describes testable user-facing behavior rather than technical implementation notes for developers.

Can I set GitHub project fields for priority and effort when creating issues with gh CLI?

Yes, you can set GitHub project fields for priority, effort, and category when creating issues. After formatting the issue body and running the gh CLI to create the ticket, the skill automatically configures these project fields for triage.

Does the ticket-creator skill work for product discovery and sprint planning?

Yes, the ticket-creator skill works for product discovery and sprint planning. It transforms vague stakeholder requests and ad-hoc brainstorming notes into well-scoped, actionable GitHub stories suitable for triage and development planning.

How do I ensure my GitHub feature requests include out-of-scope items and open questions?

To ensure GitHub feature requests include out-of-scope items and open questions, the skill enforces a specific issue body format. It interactively guides you to define these boundaries alongside acceptance criteria before running the gh CLI to create the ticket.

Do I need the gh CLI installed to create GitHub tickets from feature requests?

Yes, you need the gh CLI installed and configured because the skill relies on it to create the GitHub issue and set project fields. The CLI executes the final ticket creation after the interactive formatting process completes.