create-issue

Create or update GitHub issues from verified design documents.

4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/uta2000/feature-flow --skill create-issue-uta2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/uta2000/feature-flow/tree/main/skills/create-issue
Command: npx skills add https://github.com/uta2000/feature-flow --skill create-issue-uta2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert verified design documents into actionable GitHub issues, ensuring implementation briefs are traceable and up-to-date.

Core Features & Use Cases

  • Load the design document
  • Map sections to issue structure
  • Draft issue body and metadata (title, labels, milestone)
  • Create or update an existing issue
  • Propose next steps and alignment with design doc

Quick Start

Provide a verified design document to generate a GitHub issue for implementation.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create GitHub issues from a design document?

To create GitHub issues from a design document, you provide the verified design file to the skill. It reads the document, maps sections to issue fields, drafts metadata, and interacts with GitHub to generate the issue.

Can I update an existing GitHub issue from a design doc?

Yes, you can update an existing GitHub issue from a design doc by providing the issue number as context. The skill reads the design document and updates the issue body and metadata accordingly.

What is the process for mapping a design doc to GitHub issue metadata?

Mapping a design doc to GitHub issue metadata involves reading the document and extracting sections to draft a concise body. It automatically maps content to title, labels, and milestone for the issue.

Do I need a verified design document before generating GitHub issues?

Yes, a verified design document is required before generating GitHub issues. The skill specifically automates the creation or updating of issues from a prepared and verified feature design.

What's the best way to ensure implementation briefs are traceable to GitHub issues?

To ensure implementation briefs are traceable, convert verified design documents into actionable GitHub issues. This captures the design as an implementable issue and proposes alignment with the original design doc.