gen-specs-as-issues

Compare documentation to implementation and generate prioritized GitHub issues with specifications.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill gen-specs-as-issues-gabeujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-specs-as-issues
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/gen-specs-as-issues
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill gen-specs-as-issues-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying missing features, prioritizing them, and creating detailed, actionable GitHub issues for implementation, ensuring a structured and efficient development workflow.

Core Features & Use Cases

  • Gap Analysis: Compares project documentation against actual implementation to find missing features.
  • Prioritization: Uses a scoring matrix to rank identified gaps based on user impact, strategic alignment, and feasibility.
  • Specification Development: Creates detailed MVP-focused specifications including technical requirements and acceptance criteria.
  • GitHub Issue Creation: Generates well-structured GitHub issues with clear titles, descriptions, and dependency mapping.
  • Use Case: A product manager can use this skill to systematically identify and document new features needed for an upcoming release, ensuring all critical aspects are considered before development begins.

Quick Start

Use the gen-specs-as-issues skill to identify and create GitHub issues for missing features in the current project.

Frequently Asked Questions about gen-specs-as-issues

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

FAQPage Schema
How do I identify missing features by comparing project documentation to implementation?

Gap analysis compares project documentation against actual implementation to systematically identify missing features. It highlights discrepancies between planned specifications and current code, enabling targeted product management.

What is the best way to prioritize missing features for an upcoming software release?

Prioritizing missing features is best done using a defined scoring matrix that ranks gaps based on user impact, strategic alignment, and feasibility. This structured approach ensures critical aspects are evaluated before development begins.

How do I generate detailed GitHub issues for new feature specifications?

Generating detailed GitHub issues involves creating well-structured entries with clear titles, descriptions, and dependency mapping from MVP-focused specifications. This ensures technical requirements and acceptance criteria are clearly communicated.

Can I automatically map dependencies when creating GitHub issues for product management?

Dependency mapping is integrated directly into the GitHub issue creation process. The generated issues include dependency mapping alongside detailed titles and descriptions to ensure an efficient development workflow.

Does generating feature specs as GitHub issues require a structured approach to gap analysis?

Generating feature specs as GitHub issues requires a structured approach to gap analysis, prioritization scoring, and issue templating. This structure ensures accurate feature discovery and actionable development tasks.