tickets-batch

Create 5–20 structured GitHub issues from ticket titles in one batch.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill tickets-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tickets-batch
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/tickets-batch
Command: npx skills add https://github.com/me2resh/apexyard --skill tickets-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk ticket creation is slow and error-prone when each issue must match a strict schema, especially when you need multiple tickets filed in one go.

Core Features & Use Cases

  • Structured 5–20 ticket filing: creates multiple GitHub issues with consistent required sections by generating conformant ticket bodies from the start.
  • Shared batch context once: asks for priority, optional epic/parent reference, and optional area labels one time for the whole batch.
  • Per-ticket micro-interviews: gathers only the minimum details needed per ticket (type and one-line purpose, with an optional targeted clarification) and then files each ticket individually.

Quick Start

Use tickets-batch to file 10 startup kickoff tickets by sending the command "/tickets-batch ./backlog-batches/kickoff-tickets.md" and then confirming the batch summary before it files anything.

Frequently Asked Questions about tickets-batch

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

FAQPage Schema
How do I create multiple GitHub issues in a single batch with consistent formatting?

Batch GitHub issue creation uses a shared context step for priority and labels, then runs per-ticket micro-interviews to generate schema-conformant bodies before filing. This enforces required sections across 5–20 issues without repetitive manual prompting.

What's the best way to decompose a product roadmap into structured GitHub issues?

Roadmap decomposition into structured GitHub issues works by taking a list of ticket titles and applying schema-driven body construction. The tool asks for batch-wide context like epic references once, then gathers minimal per-ticket details to file conformant issues.

Can I use the GitHub CLI to automatically file schema-validated tickets in bulk?

Yes, bulk schema-validated ticket filing uses the GitHub CLI to call gh issue create once per ticket. It resolves the target repo via portfolio configuration, enforces required sections through validator backstops, and reports progress after each creation.

How do I avoid repetitive prompting when onboarding a repository with many kickoff tickets?

Repository onboarding with many kickoff tickets avoids repetitive prompting by collecting shared batch context once. You provide a list of titles, confirm the batch summary, and the tool handles per-ticket body generation and filing individually.

Does batch ticket generation require setting up portfolio configuration for repository resolution?

Yes, batch ticket generation requires portfolio configuration to resolve the target repository. This setup ensures the GitHub CLI calls target the correct repo before schema validation and per-ticket filing begin.

Why does schema validation matter when filing bulk GitHub issues?

Schema validation matters for bulk GitHub issues because it enforces required sections in every ticket body from the start. Validator backstops catch missing fields before the GitHub CLI files each issue, preventing malformed tickets.