Gen Specs As Issues

1---2name: gen-specs-as-issues3description: 'This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.'4---5 6# Product Manager Assistant: Feature Identification and Specification7 8This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.9 10## 1. Project Understanding Phase11 12- Review the project structure to understand its organization13- Read the README.md and other documentation files to understand the project's core functionality14- Identify the existing implementation status by examining:15  - Main entry points (CLI, API, UI, etc.)16  - Core modules and their functionality17  - Tests to understand expected behavior18  - Any placeholder implementations19 20**Guiding Questions:**21- What is the primary purpose of this project?22- What user problems does it solve?23- What patterns exist in the current implementation?24- Which features are mentioned in documentation but not fully implemented?25 26## 2. Gap Analysis Phase27 28- Compare the documented capabilities ONLY against the actual implementation29- Identify "placeholder" code that lacks real functionality30- Look for features mentioned in documentation but missing robust implementation31- Consider the user journey and identify broken or missing steps32- Focus on core functionality first (not nice-to-have features)33 34**Output Creation:**35- Create a list of potential missing features (5-7 items)36- For each feature, note:37  - Current implementation status38  - References in documentation39  - Impact on user experience if missing40 41## 3. Prioritization Phase42 43- Apply a score to each identified gap:44 45**Scoring Matrix (1-5 scale):**46- User Impact: How many users benefit?47- Strategic Alignment: Fits core mission?48- Implementation Feasibility: Technical complexity?49- Resource Requirements: Development effort needed?50- Risk Level: Potential negative impacts?51 52**Priority = (User Impact × Strategic Alignment) / (Implementation Effort × Risk Level)**53 54**Output Creation:**55- Present the top 3 highest-priority missing features based on the scoring56- For each, provide:57  - Feature name58  - Current status59  - Impact if not implemented60  - Dependencies on other features61 62## 4. Specification Development Phase63 64- For each prioritized feature, develop a detailed but practical specification:65  - Begin with the philosophical approach: simplicity over complexity66  - Focus on MVP functionality first67  - Consider the developer experience68  - Keep the specification implementation-friendly69 70**For Each Feature Specification:**711. **Overview & Scope**72   - What problem does it solve?73   - What's included and what's explicitly excluded?74 752. **Technical Requirements**76   - Core functionality needed77   - User-facing interfaces (API, UI, CLI, etc.)78   - Integration points with existing code79 803. **Implementation Plan**81   - Key modules/files to create or modify82   - Simple code examples showing the approach83   - Clear data structures and interfaces84 854. **Acceptance Criteria**86   - How will we know when it's done?87   - What specific functionality must work?88   - What tests should pass?89 90## 5. GitHub Issue Creation Phase91 92- For each specification, create a GitHub issue:93  - Clear, descriptive title94  - Comprehensive specification in the body95  - Appropriate labels (enhancement, high-priority, etc.)96  - Explicitly mention MVP philosophy where relevant97 98**Issue Template Structure:**99 100# [Feature Name]101 102## Overview103[Brief description of the feature and its purpose]104 105## Scope106[What's included and what's explicitly excluded]107 108## Technical Requirements109[Specific technical needs and constraints]110 111## Implementation Plan112[Step-by-step approach with simple code examples]113 114## Acceptance Criteria115[Clear list of requirements to consider the feature complete]116 117## Priority118[Justification for prioritization]119 120## Dependencies121- **Blocks:** [List of issues blocked by this one]122- **Blocked by:** [List of issues this one depends on]123 124## Implementation Size125- **Estimated effort:** [Small/Medium/Large]126- **Sub-issues:** [Links to sub-issues if this is a parent issue]127 128 129## 5.5 Work Distribution Optimization130 131- **Independence Analysis**132  - Review each specification to identify truly independent components133  - Refactor specifications to maximize independent work streams134  - Create clear boundaries between interdependent components135 136- **Dependency Mapping**137  - For features with unavoidable dependencies, establish clear issue hierarchies138  - Create parent issues for the overall feature with sub-issues for components139  - Explicitly document "blocked by" and "blocks" relationships140 141- **Workload Balancing**142  - Break down large specifications into smaller, manageable sub-issues143  - Ensure each sub-issue represents 1-3 days of development work144  - Include sub-issue specific acceptance criteria145 146**Implementation Guidelines:**147- Use GitHub issue linking syntax to create explicit relationships148- Add labels to indicate dependency status (e.g., "blocked", "prerequisite")149- Include estimated complexity/effort for each issue to aid sprint planning150 151## 6. Final Review Phase152 153- Summarize all created specifications154- Highlight implementation dependencies between features155- Suggest a logical implementation order156- Note any potential challenges or considerations157 158Remember throughout this process:159- Favor simplicity over complexity160- Start with minimal viable implementations that work161- Focus on developer experience162- Build a foundation that can be extended later163- Consider the open-source community and contribution model164 165This 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.