[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F4P1CX80FBGCDA934B4V4F":3,"skill-same:01M6F4P1CX80FBGCDA934B4V4F":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6F4P1CX80FBGCDA934B4V4F","gen-specs-as-issues",null,"This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgen-specs-as-issues\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"issues","gen specs as issues","as","workflow","create","prioritize","implementation","systematic","missing","guides","specifications","you","2026-11-10 10:12:30",false,"---\nname: gen-specs-as-issues\ndescription: 'This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.'\n---\n\n# Product Manager Assistant: Feature Identification and Specification\n\nThis workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.\n\n## 1. Project Understanding Phase\n\n- Review the project structure to understand its organization\n- Read the README.md and other documentation files to understand the project's core functionality\n- Identify the existing implementation status by examining:\n  - Main entry points (CLI, API, UI, etc.)\n  - Core modules and their functionality\n  - Tests to understand expected behavior\n  - Any placeholder implementations\n\n**Guiding Questions:**\n- What is the primary purpose of this project?\n- What user problems does it solve?\n- What patterns exist in the current implementation?\n- Which features are mentioned in documentation but not fully implemented?\n\n## 2. Gap Analysis Phase\n\n- Compare the documented capabilities ONLY against the actual implementation\n- Identify \"placeholder\" code that lacks real functionality\n- Look for features mentioned in documentation but missing robust implementation\n- Consider the user journey and identify broken or missing steps\n- Focus on core functionality first (not nice-to-have features)\n\n**Output Creation:**\n- Create a list of potential missing features (5-7 items)\n- For each feature, note:\n  - Current implementation status\n  - References in documentation\n  - Impact on user experience if missing\n\n## 3. Prioritization Phase\n\n- Apply a score to each identified gap:\n\n**Scoring Matrix (1-5 scale):**\n- User Impact: How many users benefit?\n- Strategic Alignment: Fits core mission?\n- Implementation Feasibility: Technical complexity?\n- Resource Requirements: Development effort needed?\n- Risk Level: Potential negative impacts?\n\n**Priority = (User Impact × Strategic Alignment) \u002F (Implementation Effort × Risk Level)**\n\n**Output Creation:**\n- Present the top 3 highest-priority missing features based on the scoring\n- For each, provide:\n  - Feature name\n  - Current status\n  - Impact if not implemented\n  - Dependencies on other features\n\n## 4. Specification Development Phase\n\n- For each prioritized feature, develop a detailed but practical specification:\n  - Begin with the philosophical approach: simplicity over complexity\n  - Focus on MVP functionality first\n  - Consider the developer experience\n  - Keep the specification implementation-friendly\n\n**For Each Feature Specification:**\n1. **Overview & Scope**\n   - What problem does it solve?\n   - What's included and what's explicitly excluded?\n\n2. **Technical Requirements**\n   - Core functionality needed\n   - User-facing interfaces (API, UI, CLI, etc.)\n   - Integration points with existing code\n\n3. **Implementation Plan**\n   - Key modules\u002Ffiles to create or modify\n   - Simple code examples showing the approach\n   - Clear data structures and interfaces\n\n4. **Acceptance Criteria**\n   - How will we know when it's done?\n   - What specific functionality must work?\n   - What tests should pass?\n\n## 5. GitHub Issue Creation Phase\n\n- For each specification, create a GitHub issue:\n  - Clear, descriptive title\n  - Comprehensive specification in the body\n  - Appropriate labels (enhancement, high-priority, etc.)\n  - Explicitly mention MVP philosophy where relevant\n\n**Issue Template Structure:**\n\n# [Feature Name]\n\n## Overview\n[Brief description of the feature and its purpose]\n\n## Scope\n[What's included and what's explicitly excluded]\n\n## Technical Requirements\n[Specific technical needs and constraints]\n\n## Implementation Plan\n[Step-by-step approach with simple code examples]\n\n## Acceptance Criteria\n[Clear list of requirements to consider the feature complete]\n\n## Priority\n[Justification for prioritization]\n\n## Dependencies\n- **Blocks:** [List of issues blocked by this one]\n- **Blocked by:** [List of issues this one depends on]\n\n## Implementation Size\n- **Estimated effort:** [Small\u002FMedium\u002FLarge]\n- **Sub-issues:** [Links to sub-issues if this is a parent issue]\n\n\n## 5.5 Work Distribution Optimization\n\n- **Independence Analysis**\n  - Review each specification to identify truly independent components\n  - Refactor specifications to maximize independent work streams\n  - Create clear boundaries between interdependent components\n\n- **Dependency Mapping**\n  - For features with unavoidable dependencies, establish clear issue hierarchies\n  - Create parent issues for the overall feature with sub-issues for components\n  - Explicitly document \"blocked by\" and \"blocks\" relationships\n\n- **Workload Balancing**\n  - Break down large specifications into smaller, manageable sub-issues\n  - Ensure each sub-issue represents 1-3 days of development work\n  - Include sub-issue specific acceptance criteria\n\n**Implementation Guidelines:**\n- Use GitHub issue linking syntax to create explicit relationships\n- Add labels to indicate dependency status (e.g., \"blocked\", \"prerequisite\")\n- Include estimated complexity\u002Feffort for each issue to aid sprint planning\n\n## 6. Final Review Phase\n\n- Summarize all created specifications\n- Highlight implementation dependencies between features\n- Suggest a logical implementation order\n- Note any potential challenges or considerations\n\nRemember throughout this process:\n- Favor simplicity over complexity\n- Start with minimal viable implementations that work\n- Focus on developer experience\n- Build a foundation that can be extended later\n- Consider the open-source community and contribution model\n\nThis 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.\n\n","# Product Manager Assistant: Feature Identification and Specification\n\nThis workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.\n\n## 1. Project Understanding Phase\n\n- Review the project structure to understand its organization\n- Read the README.md and other documentation files to understand the project's core functionality\n- Identify the existing implementation status by examining:\n  - Main entry points (CLI, API, UI, etc.)\n  - Core modules and their functionality\n  - Tests to understand expected behavior\n  - Any placeholder implementations\n\n**Guiding Questions:**\n- What is the primary purpose of this project?\n- What user problems does it solve?\n- What patterns exist in the current implementation?\n- Which features are mentioned in documentation but not fully implemented?\n\n## 2. Gap Analysis Phase\n\n- Compare the documented capabilities ONLY against the actual implementation\n- Identify \"placeholder\" code that lacks real functionality\n- Look for features mentioned in documentation but missing robust implementation\n- Consider the user journey and identify broken or missing steps\n- Focus on core functionality first (not nice-to-have features)\n\n**Output Creation:**\n- Create a list of potential missing features (5-7 items)\n- For each feature, note:\n  - Current implementation status\n  - References in documentation\n  - Impact on user experience if missing\n\n## 3. Prioritization Phase\n\n- Apply a score to each identified gap:\n\n**Scoring Matrix (1-5 scale):**\n- User Impact: How many users benefit?\n- Strategic Alignment: Fits core mission?\n- Implementation Feasibility: Technical complexity?\n- Resource Requirements: Development effort needed?\n- Risk Level: Potential negative impacts?\n\n**Priority = (User Impact × Strategic Alignment) \u002F (Implementation Effort × Risk Level)**\n\n**Output Creation:**\n- Present the top 3 highest-priority missing features based on the scoring\n- For each, provide:\n  - Feature name\n  - Current status\n  - Impact if not implemented\n  - Dependencies on other features\n\n## 4. Specification Development Phase\n\n- For each prioritized feature, develop a detailed but practical specification:\n  - Begin with the philosophical approach: simplicity over complexity\n  - Focus on MVP functionality first\n  - Consider the developer experience\n  - Keep the specification implementation-friendly\n\n**For Each Feature Specification:**\n1. **Overview & Scope**\n   - What problem does it solve?\n   - What's included and what's explicitly excluded?\n\n2. **Technical Requirements**\n   - Core functionality needed\n   - User-facing interfaces (API, UI, CLI, etc.)\n   - Integration points with existing code\n\n3. **Implementation Plan**\n   - Key modules\u002Ffiles to create or modify\n   - Simple code examples showing the approach\n   - Clear data structures and interfaces\n\n4. **Acceptance Criteria**\n   - How will we know when it's done?\n   - What specific functionality must work?\n   - What tests should pass?\n\n## 5. GitHub Issue Creation Phase\n\n- For each specification, create a GitHub issue:\n  - Clear, descriptive title\n  - Comprehensive specification in the body\n  - Appropriate labels (enhancement, high-priority, etc.)\n  - Explicitly mention MVP philosophy where relevant\n\n**Issue Template Structure:**\n\n# [Feature Name]\n\n## Overview\n[Brief description of the feature and its purpose]\n\n## Scope\n[What's included and what's explicitly excluded]\n\n## Technical Requirements\n[Specific technical needs and constraints]\n\n## Implementation Plan\n[Step-by-step approach with simple code examples]\n\n## Acceptance Criteria\n[Clear list of requirements to consider the feature complete]\n\n## Priority\n[Justification for prioritization]\n\n## Dependencies\n- **Blocks:** [List of issues blocked by this one]\n- **Blocked by:** [List of issues this one depends on]\n\n## Implementation Size\n- **Estimated effort:** [Small\u002FMedium\u002FLarge]\n- **Sub-issues:** [Links to sub-issues if this is a parent issue]\n\n\n## 5.5 Work Distribution Optimization\n\n- **Independence Analysis**\n  - Review each specification to identify truly independent components\n  - Refactor specifications to maximize independent work streams\n  - Create clear boundaries between interdependent components\n\n- **Dependency Mapping**\n  - For features with unavoidable dependencies, establish clear issue hierarchies\n  - Create parent issues for the overall feature with sub-issues for components\n  - Explicitly document \"blocked by\" and \"blocks\" relationships\n\n- **Workload Balancing**\n  - Break down large specifications into smaller, manageable sub-issues\n  - Ensure each sub-issue represents 1-3 days of development work\n  - Include sub-issue specific acceptance criteria\n\n**Implementation Guidelines:**\n- Use GitHub issue linking syntax to create explicit relationships\n- Add labels to indicate dependency status (e.g., \"blocked\", \"prerequisite\")\n- Include estimated complexity\u002Feffort for each issue to aid sprint planning\n\n## 6. Final Review Phase\n\n- Summarize all created specifications\n- Highlight implementation dependencies between features\n- Suggest a logical implementation order\n- Note any potential challenges or considerations\n\nRemember throughout this process:\n- Favor simplicity over complexity\n- Start with minimal viable implementations that work\n- Focus on developer experience\n- Build a foundation that can be extended later\n- Consider the open-source community and contribution model\n\nThis 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.\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fgithub\u002Fawesome-copilot\u002Fgen-specs-as-issues",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill gen-specs-as-issues",{"tool":51,"command":52},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill gen-specs-as-issues",{"tool":54,"command":55},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill gen-specs-as-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fgen-specs-as-issues\u002FSKILL.md",true,[],[60,74,84,93,99,106],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":70,"publishedAt":31},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[71,72,73],"model","model hierarchy","model hierarchy skill",{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":80,"publishedAt":31},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[79],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[81,82,83],"MCP","zoom","zoom mcp",{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":31},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[90,91,92,82],"sdk","zoom apps sdk","apps",{"skillNo":94,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":31},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[95],{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":31},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[104],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[101],{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":31},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[108]]