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

Creates GitHub issues for unimplemented requirements found in specification files.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-github-issues-for-unmet-specification-requirements-miyake-san
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/miyake-san/sogo-agent-platform/tree/main/skills/core/create-github-issues-for-unmet-specification-requirements
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-github-issues-for-unmet-specification-requirements-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking which specification requirements remain unimplemented is tedious and error-prone when done manually. This Skill automates the gap analysis between a specification file and the actual codebase, then files a GitHub issue for every requirement that still needs work. ## Core Features & Use Cases - Requirement Extraction: Parses a specification file to enumerate all defined requirements. - Implementation Verification: Searches the codebase and related files in the /spec/ directory to determine whether each requirement is already implemented or partially implemented. - Duplicate Prevention: Uses search_issues to check existing GitHub issues before creating new ones, avoiding redundant tickets. - Structured Issue Creation: Files one issue per unmet requirement via create_issue, using the feature_request.yml template with requirement ID, implementation guidance, and acceptance criteria. - Use Case: After drafting a product specification, run this Skill to automatically generate a backlog of GitHub issues covering every requirement the team has not yet built. ## Quick Start Analyze the specification file at spec/payments.md and create GitHub issues for every requirement that is not yet implemented in the codebase.

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 create GitHub issues from a specification file automatically?

Provide the path to your specification file and the Skill extracts every requirement, checks the codebase for existing implementations, and creates one GitHub issue per unmet requirement using the feature_request.yml template.

How to avoid duplicate GitHub issues when generating them from specs?

The Skill runs a search_issues query against the repository before creating anything. Requirements that already have matching issues are skipped, so only genuinely new unimplemented requirements produce new tickets.

Does it detect partially implemented requirements?

Yes. It searches the codebase for related code patterns and checks related files in the /spec/ directory to verify whether a requirement is fully or partially implemented before deciding to file an issue.

What issue template does it use when creating GitHub issues?

It uses the repository's feature_request.yml issue template, falling back to the default issue format if that template is unavailable. Each issue includes the requirement ID, description, implementation guidance, and acceptance criteria.

What labels are applied to the generated GitHub issues?

Generated issues are labeled as feature or enhancement as appropriate, with titles containing the requirement ID and a brief description for easy backlog triage.