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

Generate GitHub issues for unmet requirements extracted from specification files.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-github-issues-for-unmet-specification-requirements-angryconsultant
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/angryconsultant/Copilot-CLI/tree/main/skills/create-github-issues-for-unmet-specification-requirements
Command: npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-github-issues-for-unmet-specification-requirements-angryconsultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates GitHub Issues for unimplemented requirements found in specification files, enabling teams to track gaps and drive implementation.

Core Features & Use Cases

  • Analyze specification files to extract requirements
  • Compare with implemented code to identify gaps
  • Create issue per unmet requirement using a template
  • Avoid duplicate issues by searching existing issues

Quick Start

Create GitHub issues for each unmet requirement found in the specification file.

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 from specification files?

To automatically create GitHub issues from specification files, this Skill analyzes your specs, compares them against implemented code to identify gaps, and generates a dedicated issue for each unmet requirement using a standard template.

Can I generate GitHub issues for unimplemented requirements without creating duplicates?

Yes, you can generate GitHub issues for unimplemented requirements without creating duplicates. The Skill performs deduplication checks by searching existing GitHub issues before creating a new one, ensuring only unique unmet requirements are tracked.

What is the best way to track specification gaps in GitHub?

The best way to track specification gaps in GitHub is to automatically extract requirements from spec files, identify unimplemented ones, and create traceable issues. This records the requirement ID and context within a standardized issue template.

Does this tool work with specification documents stored in custom directories?

Yes, this tool works with specification documents stored in standard or custom directories. It is applicable to codebases containing specification files, such as those located in a /spec/ folder or adjacent directories within your repository.

How do I enforce one issue per requirement when generating GitHub issues from specs?

To enforce one issue per requirement when generating GitHub issues from specs, the Skill analyzes specification files and creates a single, standardized issue for each unmet requirement. It searches existing issues to prevent duplicates and records the requirement ID for traceability.