Agent skill · product strategy · github
gen-specs-as-issues
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
Why this skill is useful
Provides a structured workflow for feature identification and specification that enhances project management capabilities.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gen-specs-as-issues