Create GitHub Issues For Unmet Specification Requirements

Create GitHub Issues For Unmet Specification Requirements is an AI skill that analyzes project specifications against current implementation status and generates structured GitHub issues for unmet requirements, converting specification gaps into actionable tracking items.

What Is This?

Overview

This skill compares technical specifications, product requirement documents, or feature lists against the current state of a codebase and identifies gaps where specified behavior is missing, incomplete, or deviating from the requirement. For each gap, it generates a GitHub issue with acceptance criteria and appropriate labels, automating the tedious manual audit process.

Who Should Use This

This skill is built for project managers conducting specification compliance audits, QA engineers verifying feature completeness against requirements, development leads planning sprint work from specification gaps, and teams transitioning from specification documents to agile issue-based workflows.

Why Use It?

Problems It Solves

Specifications often exist as static documents that drift from actual implementation over time. Manually comparing a specification against code to identify gaps is error-prone and time-consuming. Creating well-structured issues with proper criteria takes additional effort.

Core Highlights

The skill performs systematic requirement-by-requirement analysis rather than spot-checking. It generates issues with consistent formatting including requirement traceability references, testable acceptance criteria, and suggested implementation approaches. Batch creation handles dozens of requirements efficiently, and duplicate detection prevents redundant issues.

How to Use It?

Basic Usage

## REQ-AUTH-001:

Password Reset Flow
Users must be able to reset their password via email verification.
The system shall send a reset link valid for 24 hours.
The reset page must enforce the password complexity policy.

## Title:

Implement password reset flow (REQ-AUTH-001)

### Description
The password reset flow specified in REQ-AUTH-001 is not fully
implemented. The current codebase is missing email verification
and the 24-hour link expiration mechanism.

### Acceptance Criteria
- [ ] Reset request sends verification email with unique token
- [ ] Reset link expires after 24 hours
- [ ] Reset page enforces password complexity policy
- [ ] Invalid or expired tokens show appropriate error message

### Labels: enhancement, auth, specification-gap

Real-World Examples

gh issue create \
  --title "Implement password reset flow (REQ-AUTH-001)" \
  --body "### Description
The password reset flow is not implemented.

### Acceptance Criteria
- [ ] Reset sends verification email
- [ ] Link expires after 24 hours
- [ ] Password complexity enforced

### Specification Reference
REQ-AUTH-001, Section 3.2" \
  --label "enhancement,specification-gap"

cat generated_issues.json | jq -c '.[]' | while read issue; do
  title=$(echo "$issue" | jq -r '.title')
  body=$(echo "$issue" | jq -r '.body')
  labels=$(echo "$issue" | jq -r '.labels')
  gh issue create --title "$title" --body "$body" --label "$labels"
done

Advanced Tips

Provide both the specification document and a summary of current implementation status for more accurate gap analysis. Include priority indicators in your specification to help the skill assign appropriate labels to generated issues. Run the analysis incrementally as specifications evolve rather than waiting for a complete audit at the end.

When to Use It?

Use Cases

Use this skill when starting implementation of a new specification and needing to create the full issue backlog, when conducting periodic compliance audits to find specification drift, when onboarding to a project and needing to identify incomplete features, or when transitioning from document-based project management to issue tracking systems.

Related Topics

Requirements traceability matrices, GitHub Projects for backlog management, specification-driven development workflows, acceptance test generation, and continuous compliance monitoring all complement the specification gap analysis this skill provides.

Important Notes

Requirements

Access to the specification document in a readable format such as Markdown, PDF, or structured text is required. Repository access with issue creation permissions is needed for automatic issue generation via the GitHub CLI. Clear, testable requirements in the specification produce the most actionable issues.

Usage Recommendations

Do: review generated issues before batch-creating them to verify accuracy and priority. Include specification section references so developers can trace issues back to source requirements. Update or close generated issues as requirements are implemented to maintain tracking accuracy.

Don't: create issues from draft specifications that are still being finalized, as this generates churn. Skip the review step when batch-creating dozens of issues. Assume the skill catches every gap, as nuanced requirements may need human interpretation.

Limitations

The skill identifies gaps based on specification text analysis and may not detect subtle implementation deviations that require runtime testing. Ambiguous or incomplete specifications produce less precise issue descriptions. The skill checks for feature presence, not code correctness.