[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MH6RQRG9Y4CAFB3RCKXGA":3,"skill-same:01M77MH6RQRG9Y4CAFB3RCKXGA":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77MH6RQRG9Y4CAFB3RCKXGA","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.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgen-specs-as-issues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","# 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",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fgen-specs-as-issues",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill gen-specs-as-issues",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill gen-specs-as-issues",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill gen-specs-as-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgen-specs-as-issues\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]