issue-creator

Transform user ideas into structured GitHub Issues with project context.

1|Updated Mar 6, 2026

Search Tags:#github #specification #requirements #issue #workflows #project-management

Ready to run

npx skills add https://github.com/zenbuapps/zenbu-powers --skill issue-creator-zenbuapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-creator
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/issue-creator
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill issue-creator-zenbuapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a user’s rough idea into a structured GitHub Issue specification by analyzing project context, existing specs (features, activities, open issues), and mapping inputs to a complete requirement document. It defaults to PM mode and can switch to Dev mode when prompted, streamlining the handoff from idea to actionable tasks.

Core Features & Use Cases

Idea expansion: From a brief idea to a complete issue body including background, goals, and acceptance criteria.
Context integration: Reads specs/features/activities/open-issues to ensure alignment and avoid duplication.
Mode switching: Defaults to PM mode; switches to Dev mode on explicit prompts to generate technical details and edge cases.

Quick Start

Describe your idea in a sentence and the skill will generate a complete GitHub Issue ready for submission.

Frequently Asked Questions about issue-creator

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

FAQPage Schema

How do I turn a rough idea into a structured GitHub issue?▼

To turn a rough idea into a structured GitHub issue, describe your idea in a sentence. The skill analyzes project context and specs to generate a complete issue body with background, objectives, acceptance criteria, and references.

How do I generate GitHub issues with detailed acceptance criteria from a brief requirement?▼

Generating GitHub issues with detailed acceptance criteria from a brief requirement involves analyzing project specs and existing context. The skill maps your input to a complete requirement document, including scope, notes, and references.

What is the difference between PM mode and Dev mode when creating project requirements?▼

The difference between PM mode and Dev mode is focus: PM mode creates high-level problem definitions, while Dev mode generates technical details and edge cases. The skill defaults to PM mode and switches on explicit prompt.

Can I use existing project specs to avoid duplicating GitHub issues?▼

Yes, you can use existing project specs to avoid duplicating GitHub issues. The skill integrates context by reading existing features, activities, and open issues to ensure alignment and prevent duplicate issue creation.

Does this issue creation workflow require manual formatting for GitHub submission?▼

No, this issue creation workflow does not require manual formatting for GitHub submission. The skill directly outputs a complete, structured issue body ready for submission, handling both high-level definitions and technical conversions.