create-github-issues-for-unmet-specification-requirements

Create GitHub issues for specification requirements that lack an existing matching issue.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-github-issues-for-unmet-specification-requirements-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-issues-for-unmet-specification-requirements
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/create-github-issues-for-unmet-specification-requirements
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-github-issues-for-unmet-specification-requirements-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub issues for specification requirements that have not yet been implemented, ensuring gaps are tracked without manual effort.

Core Features & Use Cases

  • Requirement Extraction: Parses a specification file to list all defined requirements.
  • Implementation Check: Scans the codebase to determine which requirements are unimplemented.
  • Duplicate Prevention: Searches existing GitHub issues to avoid creating duplicates.
  • Issue Generation: Opens a new issue for each unmet requirement using the feature_request.yml template.

Use case: When a new spec is added, run this skill to instantly generate tracking issues for any missing features.

Quick Start

Ask the skill to create GitHub issues for all unmet requirements in the file specs/api.yaml.

Frequently Asked Questions about create-github-issues-for-unmet-specification-requirements

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

FAQPage Schema
How do I automatically create GitHub issues for unimplemented specification requirements?

To automate GitHub issue creation for specification requirements, this skill parses a specification file, scans the codebase to find unimplemented requirements, and opens an issue for each gap using the feature_request.yml template while preventing duplicates.

How does duplicate prevention work when generating GitHub issues from a spec file?

Duplicate prevention works by searching existing GitHub issues before generating new ones. The skill scans the repository and checks current issues to ensure it only opens a new tracking issue when no matching issue already exists for that unmet requirement.

Can I use this skill to track missing features in any specification file format?

You can use this skill to track missing features by pointing it at a specification file in your repository. It parses the defined requirements from the document and scans the codebase to determine which features remain unimplemented before generating the corresponding GitHub issues.

Do I need GitHub API authentication to generate issues for unmet requirements?

You need GitHub API authentication to generate issues for unmet requirements. The skill adheres to GitHub API authentication and rate-limit requirements to successfully open new issues for specification gaps using the repository's feature_request.yml template.

What is the best way to track implementation gaps after adding a new specification?

The best way to track implementation gaps after adding a new specification is to automate issue generation. This skill instantly scans the codebase against the new spec requirements and opens a GitHub issue for each missing feature, ensuring gaps are tracked without manual effort.

What are the limitations of automating GitHub issue creation from specification files?

A limitation of automating GitHub issue creation is the dependency on GitHub API rate limits. Additionally, the skill relies on parsing the specification file and scanning the codebase to accurately determine implementation gaps, which requires the spec structure to be clearly defined.