ticket-creator

Convert implementation plans and PRDs into structured GitHub issues with labels and acceptance criteria.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill ticket-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-creator
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/ticket-creator
Command: npx skills add https://github.com/cmbays/mokumo --skill ticket-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of converting project plans, product requirements, or discovered tasks into well-defined GitHub issues, ensuring consistent formatting and essential details.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues from various input sources like implementation plans and PRDs.
  • Structured Data: Ensures issues include titles, labels (type, priority, domain), milestones, bodies, and acceptance criteria.
  • Use Case: After an implementation plan is approved, use this Skill to automatically create a batch of GitHub issues, each representing a task from the plan, complete with appropriate labels and descriptions.

Quick Start

Use the ticket-creator skill to create GitHub issues from the implementation plan located at tmp/workspace/project-x/impl-plan.md.

Frequently Asked Questions about ticket-creator

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

FAQPage Schema
How do I create GitHub issues from an implementation plan automatically?

To create GitHub issues from an implementation plan, this Skill converts plan details into structured issues with labels, acceptance criteria, and relationships. It follows an audit, suggest, and approve pattern, presenting issues for review before creation.

Do I need GitHub CLI to generate GitHub issues from a PRD?

Yes, GitHub CLI is required to generate GitHub issues from a PRD. The Skill relies on GitHub CLI and specific label taxonomy context to ensure accurate issue generation with appropriate titles, milestones, and descriptions.

Can I review GitHub issues before they are created from my project plans?

You can review GitHub issues before creation because the Skill follows an audit and approve pattern. It presents the generated issues for your review and approval, ensuring structured data like labels and acceptance criteria are correct before committing.

What is the best way to convert discovered tasks into structured GitHub issues?

The best way to convert discovered tasks into structured GitHub issues is using an automated workflow that applies a label taxonomy. This ensures each issue includes type, priority, domain, milestones, and acceptance criteria for consistent project planning.

Does generating GitHub issues from plans work without a predefined label taxonomy?

Generating GitHub issues from plans requires specific label taxonomy context for accurate results. Without the predefined labels for type, priority, and domain, the Skill cannot ensure the structured formatting and essential details needed for proper issue creation.

Why should I use an automated issue creator for developer workflows instead of manual entry?

Using an automated issue creator for developer workflows streamlines task management by converting implementation plans into batches of well-defined GitHub issues. This ensures consistent formatting, proper labels, and structured acceptance criteria, reducing manual data entry errors.