command-generate-issues

Name: command-generate-issues
Availability: InStock
Author: aroido

Generate GitHub Issues from project documentation with priorities and dependencies.

Updated Apr 22, 2026

Search Tags:#automation #project management #documentation #github issues #requirements analysis #issue generation

Ready to run

npx skills add https://github.com/aroido/vibesmith --skill command-generate-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: command-generate-issues
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/command-generate-issues
Command: npx skills add https://github.com/aroido/vibesmith --skill command-generate-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of GitHub Issues by analyzing project documentation, ensuring that all requirements and specifications are translated into actionable tasks.

Core Features & Use Cases

Automated Issue Creation: Generates GitHub Issues directly from requirements, frontend specs, and API specifications.
Dependency Mapping: Automatically identifies and links related issues based on dependencies outlined in documentation.
Prioritization: Assigns priority levels (High, Medium, Low) to issues based on their phase and importance.
Duplicate Prevention: Checks for and avoids creating duplicate issues based on title similarity.
Use Case: After writing a new feature specification, use this Skill to automatically create all necessary backend, frontend, and documentation issues in GitHub, complete with priorities and dependencies.

Quick Start

Use the command-generate-issues skill to create GitHub issues from the project's requirements document.

Frequently Asked Questions about command-generate-issues

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

FAQPage Schema

How do I generate GitHub Issues from project documentation?▼

You can generate GitHub Issues from requirements, frontend specs, and API definitions by parsing the documentation to automatically identify tasks, assign priorities, and map dependencies for project management.

Can I automatically map issue dependencies from requirements documents?▼

Yes, dependency mapping is automated by identifying and linking related issues based on dependencies outlined in your project documentation, ensuring structured task tracking.

How does duplicate prevention work when creating GitHub Issues?▼

Duplicate prevention works by checking for and avoiding the creation of duplicate GitHub Issues based on title similarity before generating new tasks from your documentation.

How are issue priorities determined from API specifications and frontend specs?▼

Issue priorities are automatically assigned High, Medium, or Low levels based on the phase and importance of the tasks identified within your project documentation.

What is the best way to translate feature specifications into actionable GitHub tasks?▼

The best way to translate feature specifications into actionable tasks is using document analysis logic to parse requirements and automatically create structured backend, frontend, and documentation issues.

Do I need API definitions to use automated issue generation?▼

No, you do not strictly need API definitions; the issue generation skill can also parse requirements and frontend specifications to identify tasks and create structured GitHub Issues.