create-issues

Create GitHub issues from Markdown execution plan steps with metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vitalwarley/hyprdots --skill create-issues-vitalwarley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issues
Source: https://github.com/vitalwarley/hyprdots/tree/main/claude-global/skills/create-issues
Command: npx skills add https://github.com/vitalwarley/hyprdots --skill create-issues-vitalwarley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual, error-prone process of converting execution plan steps in Markdown into properly formatted GitHub issues, ensuring the plan remains the source of truth and issue numbers are synchronized back into the plan.

Core Features & Use Cases

  • Parse Markdown execution plans to extract step ID, title, full description, type, max turns, wave, and explicit dependencies from tables and diagrams.
  • Generate issue bodies with Context, Spec, Acceptance Criteria, Files Likely Affected, Verification, Dependencies, and Autonomous Execution commands, and create labels and milestones when required.
  • Idempotently skip existing issues, update the plan file with created issue numbers, present a confirmation summary before creation, and produce a final summary of created issues and warnings.
  • Use Case: Turn a wave-based project plan into a set of autonomous-ready GitHub issues for engineering and QA teams, preserving acceptance criteria and verification steps.

Quick Start

Use the create-issues skill to generate GitHub issues from a Markdown plan file and confirm creation before any changes are made.

Frequently Asked Questions about create-issues

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

FAQPage Schema
How do I create GitHub issues from a Markdown execution plan?

To create GitHub issues from a Markdown execution plan, this Skill parses step tables to extract step IDs, titles, descriptions, and dependencies, then formats them into autonomous-ready issue bodies with acceptance criteria. It presents a confirmation summary before creating the issues.

Can I synchronize GitHub issue numbers back into my Markdown plan file?

Yes, you can synchronize GitHub issue numbers back into your Markdown plan file. This Skill idempotently skips existing issues during creation and automatically updates the plan file with the newly created issue numbers to keep the plan as the source of truth.

What is an autonomous-ready GitHub issue and how does it work with execution plans?

An autonomous-ready GitHub issue includes structured metadata like Context, Spec, Acceptance Criteria, Verification, Dependencies, and Autonomous Execution commands. This format is generated from parsed Markdown execution plan steps to support autonomous execution workflows.

How do I manage GitHub labels and milestones when generating issues from a plan?

When generating issues from a plan, this Skill manages GitHub labels and milestones by creating them as required during the issue generation process. It parses plan metadata to ensure each issue is correctly tagged before final creation.

Does this issue generation approach skip existing steps if I run it multiple times?

Yes, this issue generation approach is idempotent, meaning it skips existing issues if you run it multiple times. It identifies previously created issues from the plan metadata and only generates new ones, preventing duplicate entries.

What information is extracted from execution plan step tables for issue tracking?

For issue tracking, this Skill extracts the step ID, title, full description, type, max turns, wave, and explicit dependencies from execution plan step tables. This data is then structured into issue bodies with verification steps and run-autonomous metadata.