issue

Convert rough user descriptions into structured GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/oobagi/jflow --skill issue-oobagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/oobagi/jflow/tree/main/skills/issue
Command: npx skills add https://github.com/oobagi/jflow --skill issue-oobagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn rough descriptions into structured GitHub issues. Auto-scales: small requests get one lean issue, big requests get a multi-issue breakdown. Replaces both /issue and /feature.

Core Features & Use Cases

  • Auto-scale: small requests become lean issues, big requests become phased breakdowns.
  • Create one or more issues that match the description, with optional multi-issue plan for large work.
  • Use Case: Provide a description of a bug or feature; this skill generates the appropriate issue(s).

Quick Start

Describe your problem or feature briefly, and the skill will generate the appropriate GitHub issue(s).

Frequently Asked Questions about issue

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

FAQPage Schema
How do I generate structured GitHub issues from a rough feature description?

To generate structured GitHub issues, provide a rough description of your feature or bug. The skill parses and classifies the input, automatically creating a single lean issue for small tasks or a multi-issue breakdown for larger requests.

Can I automate project planning for large features by breaking them into multiple issues?

Yes, you can automate project planning for large features. The skill investigates large requests and creates a phased multi-issue breakdown, turning broad ideas into scalable GitHub issues for structured project management.

What is the best way to scale issue tracking when a task is too big for one ticket?

The best way to scale issue tracking for oversized tasks is using an auto-scaling issue generator. It classifies request size and produces a multi-issue breakdown for large work, replacing manual feature planning and issue tracking.

Do I need to format my input a specific way to create GitHub issues?

No, you do not need to format your input specifically. You can describe a problem or feature briefly in rough terms, and the skill will parse and classify the text to create the appropriate GitHub issues automatically.

When should I use an automated issue generator instead of writing tickets manually?

You should use an automated issue generator when you have a rough idea or bug description but want structured, scalable project management. It replaces manual ticket writing by creating lean issues or multi-issue plans based on request size.