New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Gen Specs As Issues

by github in github/awesome-copilot

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

OfficialMITAuto-check passedProduct & Project Management

Install Gen Specs As Issues

skills CLI
$ npx skills add github/awesome-copilot --skill gen-specs-as-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot gen-specs-as-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gen-specs-as-issues .claude/skills/gen-specs-as-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gen-specs-as-issues
GitHub stars
40k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
682 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

  • Works in 6 steps: Project Understanding Phase → Gap Analysis Phase → Prioritization Phase → …
  • Product & Project Management work in your project
  • SKILL.md covers 1. Project Understanding Phase, 2. Gap Analysis Phase, 3. Prioritization Phase and 4. Specification Development…, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gen Specs As Issues is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. It works with GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “/gen-specs-as-issues”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Project Understanding Phase
  2. Gap Analysis Phase
  3. Prioritization Phase
  4. Specification Development Phase
  5. GitHub Issue Creation Phase
  6. Final Review Phase

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gen Specs As Issues loads about 1.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 682 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 682 words, ~1,467 tokens.

Download SKILL.mdSave it as .claude/skills/gen-specs-as-issues/SKILL.md (or your agent's skills folder).
name
gen-specs-as-issues
description
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

Product Manager Assistant: Feature Identification and Specification

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

1. Project Understanding Phase

  • Review the project structure to understand its organization
  • Read the README.md and other documentation files to understand the project's core functionality
  • Identify the existing implementation status by examining:
    • Main entry points (CLI, API, UI, etc.)
    • Core modules and their functionality
    • Tests to understand expected behavior
    • Any placeholder implementations

Guiding Questions:

  • What is the primary purpose of this project?
  • What user problems does it solve?
  • What patterns exist in the current implementation?
  • Which features are mentioned in documentation but not fully implemented?

2. Gap Analysis Phase

  • Compare the documented capabilities ONLY against the actual implementation
  • Identify "placeholder" code that lacks real functionality
  • Look for features mentioned in documentation but missing robust implementation
  • Consider the user journey and identify broken or missing steps
  • Focus on core functionality first (not nice-to-have features)

Output Creation:

  • Create a list of potential missing features (5-7 items)
  • For each feature, note:
    • Current implementation status
    • References in documentation
    • Impact on user experience if missing

3. Prioritization Phase

  • Apply a score to each identified gap:

Scoring Matrix (1-5 scale):

  • User Impact: How many users benefit?
  • Strategic Alignment: Fits core mission?
  • Implementation Feasibility: Technical complexity?
  • Resource Requirements: Development effort needed?
  • Risk Level: Potential negative impacts?

Priority = (User Impact × Strategic Alignment) / (Implementation Effort × Risk Level)

Output Creation:

  • Present the top 3 highest-priority missing features based on the scoring
  • For each, provide:
    • Feature name
    • Current status
    • Impact if not implemented
    • Dependencies on other features

4. Specification Development Phase

  • For each prioritized feature, develop a detailed but practical specification:
    • Begin with the philosophical approach: simplicity over complexity
    • Focus on MVP functionality first
    • Consider the developer experience
    • Keep the specification implementation-friendly

For Each Feature Specification:

  1. Overview & Scope

    • What problem does it solve?
    • What's included and what's explicitly excluded?

  2. Technical Requirements

    • Core functionality needed
    • User-facing interfaces (API, UI, CLI, etc.)
    • Integration points with existing code

  3. Implementation Plan

    • Key modules/files to create or modify
    • Simple code examples showing the approach
    • Clear data structures and interfaces

  4. Acceptance Criteria

    • How will we know when it's done?
    • What specific functionality must work?
    • What tests should pass?

5. GitHub Issue Creation Phase

  • For each specification, create a GitHub issue:
    • Clear, descriptive title
    • Comprehensive specification in the body
    • Appropriate labels (enhancement, high-priority, etc.)
    • Explicitly mention MVP philosophy where relevant

Issue Template Structure:

[Feature Name]

Show full SKILL.md (274 more words)Show less

Overview

[Brief description of the feature and its purpose]

Scope

[What's included and what's explicitly excluded]

Technical Requirements

[Specific technical needs and constraints]

Implementation Plan

[Step-by-step approach with simple code examples]

Acceptance Criteria

[Clear list of requirements to consider the feature complete]

Priority

[Justification for prioritization]

Dependencies

  • Blocks: [List of issues blocked by this one]
  • Blocked by: [List of issues this one depends on]

Implementation Size

  • Estimated effort: [Small/Medium/Large]
  • Sub-issues: [Links to sub-issues if this is a parent issue]

5.5 Work Distribution Optimization

  • Independence Analysis

    • Review each specification to identify truly independent components
    • Refactor specifications to maximize independent work streams
    • Create clear boundaries between interdependent components

  • Dependency Mapping

    • For features with unavoidable dependencies, establish clear issue hierarchies
    • Create parent issues for the overall feature with sub-issues for components
    • Explicitly document "blocked by" and "blocks" relationships

  • Workload Balancing

    • Break down large specifications into smaller, manageable sub-issues
    • Ensure each sub-issue represents 1-3 days of development work
    • Include sub-issue specific acceptance criteria

Implementation Guidelines:

  • Use GitHub issue linking syntax to create explicit relationships
  • Add labels to indicate dependency status (e.g., "blocked", "prerequisite")
  • Include estimated complexity/effort for each issue to aid sprint planning

6. Final Review Phase

  • Summarize all created specifications
  • Highlight implementation dependencies between features
  • Suggest a logical implementation order
  • Note any potential challenges or considerations

Remember throughout this process:

  • Favor simplicity over complexity
  • Start with minimal viable implementations that work
  • Focus on developer experience
  • Build a foundation that can be extended later
  • Consider the open-source community and contribution model

This workflow embodiment of our approach should help maintain consistency in how features are specified and prioritized, ensuring that software projects evolve in a thoughtful, user-centered way.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/gen-specs-as-issues of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gen Specs As Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gen Specs As Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gen Specs As Issues this skillgithub/awesome-copilot40k1 repos~1.5kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Release ValidationMesh-LLM/mesh-llm3.5k—~2.6kAutomated safety check: PassApache-2.0
Final Release Reviewopenai/openai-agents-python30k—~5.4kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k—~5.7kAutomated safety check: PassMIT
Project Managerpwrdrvr/openclaw-codex-app-server265—~1.5kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Release Validation

    Mesh-LLM/mesh-llm

    A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…

    3.5k GitHub stars~2.6k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Final Release Review

    openai/openai-agents-python

    Official

    Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.

    30k GitHub stars~5.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Project Manager

    pwrdrvr/openclaw-codex-app-server

    Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.

    265 GitHub stars~1.5k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Create Issue

    tradingstrategy-ai/frontend

    Creates a new GitHub issue with structured user story format, acceptance criteria, and project integration.

    150 GitHub stars~607 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Gen Specs As Issues

What does Gen Specs As Issues do?

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation. Gen Specs As Issues is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

When should I use Gen Specs As Issues?

Gen Specs As Issues fits situations like: product & Project Management work in your project.

How do I install Gen Specs As Issues in Claude Code?

Run `npx skills add github/awesome-copilot --skill gen-specs-as-issues -a claude-code`. Or copy the skill folder (skills/gen-specs-as-issues in github/awesome-copilot) into .claude/skills/gen-specs-as-issues in your project. Claude Code loads it when a task matches its description.

How do I install Gen Specs As Issues in Codex?

Run `npx skills add github/awesome-copilot --skill gen-specs-as-issues -a codex`. Or copy the skill folder (skills/gen-specs-as-issues in github/awesome-copilot) into .agents/skills/gen-specs-as-issues in your project. Codex loads it when a task matches its description.

Can I use Gen Specs As Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill gen-specs-as-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gen-specs-as-issues, .gemini/skills/gen-specs-as-issues, .github/skills/gen-specs-as-issues and .opencode/skills/gen-specs-as-issues in your project.

What does Gen Specs As Issues need to run?

SKILL.md names no scripts, command-line tools or credentials: Gen Specs As Issues is instructions for the agent only.

Does Gen Specs As Issues access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gen Specs As Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gen Specs As Issues use?

Gen Specs As Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gen Specs As Issues use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gen Specs As Issues?

Skills that share tags, products or a category with Gen Specs As Issues: CCPM Project Management (automazeio/ccpm, 8.4k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Ouroboros PM Interview (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gen Specs As Issues?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.