github-issue-gen

Generate GitHub issues and epics from project requirements.

1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/Benmore-Studio/Benmore-Meridian --skill github-issue-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-gen
Source: https://github.com/Benmore-Studio/Benmore-Meridian/tree/main/skills/github-issue-gen
Command: npx skills add https://github.com/Benmore-Studio/Benmore-Meridian --skill github-issue-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating and organizing GitHub issues and epics from high-level project goals is tedious and error-prone; this Skill automates the whole workflow to produce ready-to-use issue hierarchies.

Core Features & Use Cases

  • Epic templates: Create scalable templates for feature sets and relate them to multiple issues and milestones.
  • Sprint-ready tickets: Generate linked issues with estimates, priorities, and dependencies aligned to project phases.
  • Project planning across repos: Produce consistent issue structures that can be imported into multiple repositories and tracked in Epics.

Quick Start

Provide the project brief to generate the initial set of GitHub issues and epics.

Frequently Asked Questions about github-issue-gen

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

FAQPage Schema
How do I auto-generate GitHub issues and epics from project requirements?

You can auto-generate GitHub issues and epics by providing a project brief to the Skill, which then produces structured issue hierarchies with linked sub-issues, estimates, and dependencies aligned to project phases.

What is the best way to organize GitHub issues into epics for sprint planning?

Organizing GitHub issues into epics for sprint planning is best handled by applying epic templates that relate multiple tickets to milestones, generating linked issues with priorities, sizing, and status tracking patterns.

Can I generate consistent GitHub issue structures across multiple repositories?

Yes, you can generate consistent GitHub issue structures across multiple repositories by producing standardized issue hierarchies from project requirements that can be imported into different repos and tracked within epics.

Does this approach work with the gh-sub-issue extension for GitHub project management?

Yes, this approach works with the gh-sub-issue extension by supporting sub-issue generation and dependency tracking natively, allowing generated epics and tickets to integrate directly with existing GitHub project management workflows.

What do I need to provide to generate sprint-ready GitHub tickets and dependencies?

To generate sprint-ready GitHub tickets and dependencies, you need to provide a high-level project brief or feature breakdown, which the Skill uses to apply epic templates and output tickets with estimates and assignments.