skills.rest
afonsoft
afonsoftCOMMUNITY
Explore all skills by this author →
Website𝕏@afonsoftGitHub

create-issues

Convert roadmaps, PRDs, and SPEC files into linked GitHub Issues.

Updated Jul 21, 2026
Search Tags:#roadmap#github issues#gh cli#spec-driven development#slices#issue automation#epic tracking
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill create-issues-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issues
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/create-issues
Command: npx skills add https://github.com/afonsoft/gamehub --skill create-issues-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning approved plans, specs, and Epics into trackable work items is manual and error-prone. This Skill converts roadmaps and SPEC files into stable, linked, verifiable GitHub Issues using the gh CLI, keeping Epics, slices, and the roadmap in sync. ## Core Features & Use Cases - Epic Traceability Contract: Assigns stable E## identifiers, creates matching GitHub Issues, and writes direct links back into the roadmap or spec. - Vertical Slice Decomposition: Splits approved Epics into small, complete slices marked as HITL or AFK with explicit Blocked-by dependencies. - SDD Issue Templates: Generates Epic and slice issue bodies from .specs/SPEC-*.md files using the bundled spec-sdd-template reference. - Use Case: After approving a SPEC for a new feature, run this Skill to create the Epic Issue, publish child slice Issues in dependency order, and update ORCHESTRATOR-ROADMAP.md with links. ## Quick Start Use the create-issues skill to turn the approved SPEC file in .specs into a linked Epic and slice Issues on GitHub.

Frequently Asked Questions about create-issues

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

FAQPage Schema
How do I turn a PRD or spec into GitHub Issues?▼

Read the roadmap or .specs/SPEC-*.md file, assign each Epic a stable E## identifier, then create Epic and slice Issues with gh issue create. Update the roadmap with direct links to each created Issue.

How to create linked GitHub Issues with the gh CLI?▼

Use gh issue create with --title, --label, and --body-file to create Issues, then link dependencies with gh issue edit <number> --add-linked-issue <number> --link-type blocked_by. Capture returned issue numbers to reference them in child slices.

What are the prerequisites for using this Skill?▼

The gh CLI must be installed and authenticated, the origin remote must point to the correct GitHub repository, and a roadmap or SPEC file must exist. Verify access with gh auth status and gh repo view before creating Issues.

When should I not use this Skill for GitHub Issues?▼

Do not use it when the only task is closing or modifying existing Issues, since that is done directly on GitHub. Also stop when GitHub access is unconfirmed or when no roadmap or spec exists as a source of truth.

Why must Epic IDs never be reused or renumbered?▼

Stable E## identifiers keep traceability between the roadmap, GitHub Issues, and specs even after an Epic is done. The GitHub Issue number does not replace the Epic ID, so E10 stays stable even if the Issue is edited.

Related Skills

Explore More Product & Management Skills→
jeremylightsmithjeremylightsmith

brainstorm

Turns feature ideas into approved designs through structured clarifying dialogue.

Community
Advanced
workinprogress-aiworkinprogress-ai

devenv-update-roadmap

Synchronize roadmap Markdown files with GitHub issue and pull request states.

Official
Advanced
shimaMatzshimaMatz

kiro-spec-batch

Orchestrates automated spec generation for roadmap features via dependency waves.

Community
Advanced
chohra-medchohra-med
28

spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

Community
Advanced