github-feature-ticket-generator

Generate structured GitHub feature tickets with Common, Frontend, Backend, and Infra sections.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Mockly-Company/mockly-mobile --skill github-feature-ticket-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-feature-ticket-generator
Source: https://github.com/Mockly-Company/mockly-mobile/tree/main/.claude/skills/github-issue-generator
Command: npx skills add https://github.com/Mockly-Company/mockly-mobile --skill github-feature-ticket-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically generates structured GitHub feature tickets from concise user ideas, enabling clear planning and collaboration.

Core Features & Use Cases

  • Structured Ticket: FE/BE/Common/Infra sections with checkboxes.
  • Category-specific templates: Respects framework guides and category-specific sections.
  • Reference templates: Uses templates from references/ to standardize tickets.

Quick Start

Provide a short feature idea like "로그인 기능" and the tool will output a complete ticket ready for GitHub.

Frequently Asked Questions about github-feature-ticket-generator

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

FAQPage Schema
How do I generate GitHub feature tickets from ideas automatically?

This skill generates structured GitHub feature tickets directly from concise feature descriptions. It creates multi-section Markdown tickets with Common, Frontend, Backend, and Infra sections including checklists, then outputs them ready for creation via GitHub CLI with consistent schema enforcement and required options (--repo, --project, --type Feature, --status Backlog).

What sections does an automated GitHub ticket include?

Generated tickets include Common, Frontend, Backend, and Infra sections, each with category-specific templates and checkboxes. The skill enforces task granularity and uses reference templates to standardize structure across tickets, ensuring consistent planning and collaboration across teams.

Can I use this for planning GitHub issues in a project board?

Yes. The skill outputs tickets formatted for direct creation in GitHub project boards via gh issue create. It enforces the defined ticket schema and applies required GitHub CLI options (--project Mockly, --type Feature, --status Backlog) to ensure tickets integrate seamlessly with your project workflow.

Do I need to know Markdown to create tickets with this skill?

No. You provide a plain-language feature description and the skill generates complete Markdown-formatted tickets with proper sections and checkboxes. The output is ready to paste into GitHub without manual formatting.

How does this ensure consistent ticket quality across a team?

The skill applies category-specific templates and enforces a defined ticket schema for all outputs. It respects framework guides and standardizes section patterns, task granularity, and GitHub CLI options, so every generated ticket follows the same structure and requirements.