gen-specs-as-issues

Analyze repositories to identify missing features and generate GitHub-ready issue templates.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill gen-specs-as-issues-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-specs-as-issues
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/gen-specs-as-issues
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill gen-specs-as-issues-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps product teams and contributors identify missing or underspecified features in a codebase, prioritize them by impact and effort, and create developer-ready specifications and GitHub issues to drive implementation.

Core Features & Use Cases

  • Gap analysis: Compare README, docs, and repository structure against implemented code to list missing features and placeholder functionality.
  • Prioritization: Apply a simple scoring matrix to rank gaps by user impact, strategic alignment, feasibility, resource needs, and risk.
  • Specification & Issue Creation: Produce concise MVP-focused specifications, implementation plans, acceptance criteria, and ready-to-post GitHub issue templates.
  • Use Case: For an open-source CLI project with spotty documentation, generate the top three prioritized feature specs with sub-issues and estimated effort to bootstrap contributor work.

Quick Start

Ask the assistant to analyze the repository, list five missing features with status and references, prioritize them using the scoring matrix, and generate GitHub-ready issue bodies for the top three.

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 product features and turn them into GitHub issues?

To identify missing product features and turn them into GitHub issues, analyze repository structure and documentation to find gaps, prioritize them using a scoring matrix, and generate ready-to-post issue templates with acceptance criteria and implementation plans.

What is the best way to prioritize product backlog gaps from a codebase?

The best way to prioritize product backlog gaps is to apply a scoring matrix that ranks missing features by user impact, strategic alignment, feasibility, resource needs, and risk, translating high-priority items into developer-ready specifications.

How does gap analysis work for open-source CLI and API projects?

Gap analysis for open-source CLI and API projects works by comparing README files and documentation against implemented code to list missing features, placeholder functionality, and underspecified entry points during discovery.

Can I generate developer-ready specifications for internal software projects?

Yes, you can generate developer-ready specifications for internal software projects by documenting missing features, creating concise MVP-focused specs, implementation plans, and acceptance criteria to drive implementation during backlog grooming.

Does this workflow produce acceptance criteria and implementation plans for GitHub issues?

Yes, this workflow produces GitHub-ready issue templates that include concise MVP-focused specifications, implementation plans, and acceptance criteria to bootstrap contributor work and drive development.