Create GitHub Issues for Unmet Specification Requirements

Create GitHub Issues for unimplemented requirements in the specification at ${file}.

Process

Analyze specification file to extract all requirements
Check codebase implementation status for each requirement
Search existing issues using search_issues to avoid duplicates
Create new issue per unimplemented requirement using create_issue
Use feature_request.yml template (fallback to default)

Requirements

One issue per unimplemented requirement from specification
Clear requirement ID and description mapping
Include implementation guidance and acceptance criteria
Verify against existing issues before creation

Issue Content

Title: Requirement ID and brief description
Description: Detailed requirement, implementation method, and context
Labels: feature, enhancement (as appropriate)

Implementation Check

Search codebase for related code patterns
Check related specification files in /spec/ directory
Verify requirement isn't partially implemented

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

52/100

Grade

C

Adequate

Safety

60

Quality

48

Clarity

65

Completeness

38

Summary

This skill guides an agent to extract unimplemented requirements from a specification file, validate them against a codebase, search for duplicate issues, and create GitHub Issues for each unmet requirement using a feature_request.yml template. It operates within the scope of a single project repository and uses GitHub API operations (search, create) to manage feature tracking.

Detected Capabilities

specification file readcodebase searchgithub api: search_issuesgithub api: create_issuerequirement extraction and analysis

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

create feature request issuesextract specification requirementsautomate issue creationspecification compliance trackingunimplemented requirement tracking

Risk Signals

INFO

GitHub API operations (search_issues, create_issue) with no explicit authentication or scope guardrails documented

Process section, steps 3-4

WARNING

Specification file path is dynamically referenced (${file}) with no validation constraints documented

Description and step 1

WARNING

Codebase search scope not explicitly bounded — could traverse large directories without limits

Implementation Check section

Use Cases

Create feature request issues from specification gaps
Automate requirement tracking for unimplemented features
Bulk issue creation from specification analysis
Ensure specification compliance through GitHub tracking
Prevent duplicate feature requests via deduplication

Quality Notes

Skill describes the workflow clearly but lacks concrete implementation details (e.g., how to parse specification formats, how to identify 'unimplemented' status)
No error handling documented for edge cases: unparseable specs, API rate limits, malformed requirements, or failures during issue creation
Template fallback strategy mentioned ('use feature_request.yml template, fallback to default') but the fallback behavior is not defined
Missing concrete examples of requirement extraction and how the agent would validate existing issues to avoid duplicates
No guidance on handling partial implementations or skip criteria for certain requirements
Deduplication strategy relies on 'search_issues' but search criteria/query construction is not documented
Specification file format assumptions not stated (markdown, YAML, JSON, etc.)
No documented limits on number of issues to create in a single run (could create many issues)

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

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