issues

Create GitHub Issues from project specifications with milestone and label assignment.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/wutongshenqiu/prism --skill issues-wutongshenqiu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/wutongshenqiu/prism/tree/main/.agents/skills/issues
Command: npx skills add https://github.com/wutongshenqiu/prism --skill issues-wutongshenqiu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of GitHub Issues from specifications, streamlining the process of issue tracking and project management.

Core Features & Use Cases

  • Automated Issue Creation: Generate GitHub Issues directly from project specifications.
  • Milestone and Label Management: Optionally assign milestones and create labels to organize issues.
  • Task Breakdown: Break down specifications into actionable tasks and sub-tasks.

Quick Start

Generate GitHub Issues from the spec 'SPEC-123' with the milestone 'Q1 Release'.

Frequently Asked Questions about issues

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

FAQPage Schema
How do I automate GitHub Issue creation from a project specification?

Automating GitHub Issue creation from a project specification involves parsing your spec file to generate issues, assign milestones, and create labels using the GitHub API. This process breaks down specifications into actionable tasks and sub-tasks.

Do I need GitHub API access to generate issues from specifications?

Yes, GitHub API access is required to generate issues from specifications. You must also provide a specification file so the automation tool can parse project requirements, assign milestones, and create labels on your repository.

Can I assign milestones and create labels when automating issue tracking?

Yes, you can assign milestones and create labels when automating issue tracking. The process parses your specification file to optionally organize generated GitHub Issues by assigning relevant milestones and creating appropriate labels.

What is the best way to break down specifications into actionable GitHub tasks?

The best way to break down specifications into actionable GitHub tasks is using an automated issue creation tool. It parses your specification file to generate GitHub Issues, handling task breakdown, milestone assignment, and label creation directly.

Does automated issue generation work without a specification file?

No, automated issue generation does not work without a specification file. A valid specification file is a required dependency to parse project requirements, break them into sub-tasks, and automate GitHub Issue creation successfully.