issue-creator

Converts subtasks from task.md into GitHub issues and updates the task document with references.

Updated Mar 24, 2026

Search Tags:#automation #planning #github #backlog #issue #task-management

Ready to run

npx skills add https://github.com/balamuru/antigravity-dev-skills --skill issue-creator-balamuru

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-creator
Source: https://github.com/balamuru/antigravity-dev-skills/tree/main/.agents/skills/issue-creator
Command: npx skills add https://github.com/balamuru/antigravity-dev-skills --skill issue-creator-balamuru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Manually turning task plans into trackable work items is error-prone and hard to audit. This skill ensures every sub-task is captured as an external GitHub issue for visibility and accountability.

Core Features & Use Cases

Automated task breakdown: Converts subtasks and checklists in task.md into individual GitHub issues with clear titles and descriptions.
Context preservation: Propagates relevant project context from requirements.md or the task artifact into issue bodies.
Reconciliation: Updates the task.md with references to created issues to maintain a bi-directional trace.

Quick Start

Use the issue-creator to translate your active task.md into GitHub issues and link them back in the task document.

Frequently Asked Questions about issue-creator

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

FAQPage Schema

How do I convert a markdown task plan into trackable GitHub issues?▼

You can convert a task.md file into GitHub issues by reading the artifact, generating individual issues with titles and descriptions, and updating the document with new issue references.

Can I automatically sync subtasks from a task.md file to a GitHub backlog?▼

Yes, you can sync subtasks to a GitHub backlog by parsing the task.md artifact, creating corresponding GitHub issues for visibility, and maintaining bi-directional trace by linking them back.

Do I need the gh command line tool to automate GitHub issue creation?▼

Yes, you need the gh command line tool installed to automate GitHub issue creation. The skill depends on the gh CLI to interact with your repository and generate the trackable issues.

How does context from requirements documents get preserved when creating GitHub issues?▼

Context is preserved when creating GitHub issues by propagating relevant project information from requirements.md or the task artifact directly into the body of each generated issue.

What is the best way to maintain traceability between a task plan and GitHub issues?▼

The best way to maintain traceability is through reconciliation. After generating issues, the skill updates the task.md with references to the created issues to maintain a bi-directional trace.