[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EACS8955XQF9RAM4RQCSYB":3,"skill-same:01M6EACS8955XQF9RAM4RQCSYB":61},{"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":23,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6EACS8955XQF9RAM4RQCSYB","create_PRD",null,"Create a Product Requirements Document from conversation","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FHarmeet10000\u002Fskills\u002Fcreate_PRD\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30],"create","prd","create prd","product","document","conversation","requirements","2026-11-10 10:12:30",false,"---\ndescription: Create a Product Requirements Document from conversation\nargument-hint: [output-filename]\n---\n\n# Create PRD: Generate Product Requirements Document\n\n## Overview\n\nGenerate a comprehensive Product Requirements Document (PRD) based on the current conversation context and requirements discussed. Use the structure and sections defined below to create a thorough, professional PRD.\n\n## Output File\n\nWrite the PRD to: `$ARGUMENTS` (default: `PRD.md`)\n\n## PRD Structure\n\nCreate a well-structured PRD with the following sections. Adapt depth and detail based on available information:\n\n### Required Sections\n\n**1. Executive Summary**\n- Concise product overview (2-3 paragraphs)\n- Core value proposition\n- MVP goal statement\n\n**2. Mission**\n- Product mission statement\n- Core principles (3-5 key principles)\n\n**3. Target Users**\n- Primary user personas\n- Technical comfort level\n- Key user needs and pain points\n\n**4. MVP Scope**\n- **In Scope:** Core functionality for MVP (use ✅ checkboxes)\n- **Out of Scope:** Features deferred to future phases (use ❌ checkboxes)\n- Group by categories (Core Functionality, Technical, Integration, Deployment)\n\n**5. User Stories**\n- Primary user stories (5-8 stories) in format: \"As a [user], I want to [action], so that [benefit]\"\n- Include concrete examples for each story\n- Add technical user stories if relevant\n\n**6. Core Architecture & Patterns**\n- High-level architecture approach\n- Directory structure (if applicable)\n- Key design patterns and principles\n- Technology-specific patterns\n\n**7. Tools\u002FFeatures**\n- Detailed feature specifications\n- If building an agent: Tool designs with purpose, operations, and key features\n- If building an app: Core feature breakdown\n\n**8. Technology Stack**\n- Backend\u002FFrontend technologies with versions\n- Dependencies and libraries\n- Optional dependencies\n- Third-party integrations\n\n**9. Security & Configuration**\n- Authentication\u002Fauthorization approach\n- Configuration management (environment variables, settings)\n- Security scope (in-scope and out-of-scope)\n- Deployment considerations\n\n**10. API Specification** (if applicable)\n- Endpoint definitions\n- Request\u002Fresponse formats\n- Authentication requirements\n- Example payloads\n\n**11. Success Criteria**\n- MVP success definition\n- Functional requirements (use ✅ checkboxes)\n- Quality indicators\n- User experience goals\n\n**12. Implementation Phases**\n- Break down into 3-4 phases\n- Each phase includes: Goal, Deliverables (✅ checkboxes), Validation criteria\n- Realistic timeline estimates\n\n**13. Future Considerations**\n- Post-MVP enhancements\n- Integration opportunities\n- Advanced features for later phases\n\n**14. Risks & Mitigations**\n- 3-5 key risks with specific mitigation strategies\n\n**15. Appendix** (if applicable)\n- Related documents\n- Key dependencies with links\n- Repository\u002Fproject structure\n\n## Instructions\n\n### 1. Extract Requirements\n- Review the entire conversation history\n- Identify explicit requirements and implicit needs\n- Note technical constraints and preferences\n- Capture user goals and success criteria\n\n### 2. Synthesize Information\n- Organize requirements into appropriate sections\n- Fill in reasonable assumptions where details are missing\n- Maintain consistency across sections\n- Ensure technical feasibility\n\n### 3. Write the PRD\n- Use clear, professional language\n- Include concrete examples and specifics\n- Use markdown formatting (headings, lists, code blocks, checkboxes)\n- Add code snippets for technical sections where helpful\n- Keep Executive Summary concise but comprehensive\n\n### 4. Quality Checks\n- ✅ All required sections present\n- ✅ User stories have clear benefits\n- ✅ MVP scope is realistic and well-defined\n- ✅ Technology choices are justified\n- ✅ Implementation phases are actionable\n- ✅ Success criteria are measurable\n- ✅ Consistent terminology throughout\n\n## Style Guidelines\n\n- **Tone:** Professional, clear, action-oriented\n- **Format:** Use markdown extensively (headings, lists, code blocks, tables)\n- **Checkboxes:** Use ✅ for in-scope items, ❌ for out-of-scope\n- **Specificity:** Prefer concrete examples over abstract descriptions\n- **Length:** Comprehensive but scannable (typically 30-60 sections worth of content)\n\n## Output Confirmation\n\nAfter creating the PRD:\n1. Confirm the file path where it was written\n2. Provide a brief summary of the PRD contents\n3. Highlight any assumptions made due to missing information\n4. Suggest next steps (e.g., review, refinement, planning)\n\n## Notes\n\n- If critical information is missing, ask clarifying questions before generating\n- Adapt section depth based on available details\n- For highly technical products, emphasize architecture and technical stack\n- For user-facing products, emphasize user stories and experience\n- This command contains the complete PRD template structure - no external references needed\n","# Create PRD: Generate Product Requirements Document\n\n## Overview\n\nGenerate a comprehensive Product Requirements Document (PRD) based on the current conversation context and requirements discussed. Use the structure and sections defined below to create a thorough, professional PRD.\n\n## Output File\n\nWrite the PRD to: `$ARGUMENTS` (default: `PRD.md`)\n\n## PRD Structure\n\nCreate a well-structured PRD with the following sections. Adapt depth and detail based on available information:\n\n### Required Sections\n\n**1. Executive Summary**\n- Concise product overview (2-3 paragraphs)\n- Core value proposition\n- MVP goal statement\n\n**2. Mission**\n- Product mission statement\n- Core principles (3-5 key principles)\n\n**3. Target Users**\n- Primary user personas\n- Technical comfort level\n- Key user needs and pain points\n\n**4. MVP Scope**\n- **In Scope:** Core functionality for MVP (use ✅ checkboxes)\n- **Out of Scope:** Features deferred to future phases (use ❌ checkboxes)\n- Group by categories (Core Functionality, Technical, Integration, Deployment)\n\n**5. User Stories**\n- Primary user stories (5-8 stories) in format: \"As a [user], I want to [action], so that [benefit]\"\n- Include concrete examples for each story\n- Add technical user stories if relevant\n\n**6. Core Architecture & Patterns**\n- High-level architecture approach\n- Directory structure (if applicable)\n- Key design patterns and principles\n- Technology-specific patterns\n\n**7. Tools\u002FFeatures**\n- Detailed feature specifications\n- If building an agent: Tool designs with purpose, operations, and key features\n- If building an app: Core feature breakdown\n\n**8. Technology Stack**\n- Backend\u002FFrontend technologies with versions\n- Dependencies and libraries\n- Optional dependencies\n- Third-party integrations\n\n**9. Security & Configuration**\n- Authentication\u002Fauthorization approach\n- Configuration management (environment variables, settings)\n- Security scope (in-scope and out-of-scope)\n- Deployment considerations\n\n**10. API Specification** (if applicable)\n- Endpoint definitions\n- Request\u002Fresponse formats\n- Authentication requirements\n- Example payloads\n\n**11. Success Criteria**\n- MVP success definition\n- Functional requirements (use ✅ checkboxes)\n- Quality indicators\n- User experience goals\n\n**12. Implementation Phases**\n- Break down into 3-4 phases\n- Each phase includes: Goal, Deliverables (✅ checkboxes), Validation criteria\n- Realistic timeline estimates\n\n**13. Future Considerations**\n- Post-MVP enhancements\n- Integration opportunities\n- Advanced features for later phases\n\n**14. Risks & Mitigations**\n- 3-5 key risks with specific mitigation strategies\n\n**15. Appendix** (if applicable)\n- Related documents\n- Key dependencies with links\n- Repository\u002Fproject structure\n\n## Instructions\n\n### 1. Extract Requirements\n- Review the entire conversation history\n- Identify explicit requirements and implicit needs\n- Note technical constraints and preferences\n- Capture user goals and success criteria\n\n### 2. Synthesize Information\n- Organize requirements into appropriate sections\n- Fill in reasonable assumptions where details are missing\n- Maintain consistency across sections\n- Ensure technical feasibility\n\n### 3. Write the PRD\n- Use clear, professional language\n- Include concrete examples and specifics\n- Use markdown formatting (headings, lists, code blocks, checkboxes)\n- Add code snippets for technical sections where helpful\n- Keep Executive Summary concise but comprehensive\n\n### 4. Quality Checks\n- ✅ All required sections present\n- ✅ User stories have clear benefits\n- ✅ MVP scope is realistic and well-defined\n- ✅ Technology choices are justified\n- ✅ Implementation phases are actionable\n- ✅ Success criteria are measurable\n- ✅ Consistent terminology throughout\n\n## Style Guidelines\n\n- **Tone:** Professional, clear, action-oriented\n- **Format:** Use markdown extensively (headings, lists, code blocks, tables)\n- **Checkboxes:** Use ✅ for in-scope items, ❌ for out-of-scope\n- **Specificity:** Prefer concrete examples over abstract descriptions\n- **Length:** Comprehensive but scannable (typically 30-60 sections worth of content)\n\n## Output Confirmation\n\nAfter creating the PRD:\n1. Confirm the file path where it was written\n2. Provide a brief summary of the PRD contents\n3. Highlight any assumptions made due to missing information\n4. Suggest next steps (e.g., review, refinement, planning)\n\n## Notes\n\n- If critical information is missing, ask clarifying questions before generating\n- Adapt section depth based on available details\n- For highly technical products, emphasize architecture and technical stack\n- For user-facing products, emphasize user stories and experience\n- This command contains the complete PRD template structure - no external references needed\n",{"description":7,"argument-hint":36},[37],"output-filename","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002FHarmeet10000\u002Fskills\u002Fcreate_PRD",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill create_PRD",{"tool":53,"command":54},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill create_PRD",{"tool":56,"command":57},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill create_PRD","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002FHarmeet10000\u002Fskills\u002Fcreate_PRD\u002FSKILL.md",true,[],[62,76,86,95,101,108],{"skillNo":63,"name":64,"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":65,"categories":66,"keywords":72,"publishedAt":31},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[73,74,75],"model","model hierarchy","model hierarchy skill",{"skillNo":77,"name":78,"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":79,"categories":80,"keywords":82,"publishedAt":31},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[81],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[83,84,85],"MCP","zoom","zoom mcp",{"skillNo":87,"name":88,"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":89,"categories":90,"keywords":91,"publishedAt":31},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[92,93,94,84],"sdk","zoom apps sdk","apps",{"skillNo":96,"name":97,"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":98,"categories":99,"keywords":100,"publishedAt":31},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[97],{"skillNo":102,"name":103,"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":104,"categories":105,"keywords":107,"publishedAt":31},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[106],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[103],{"skillNo":109,"name":110,"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":111,"categories":112,"keywords":113,"publishedAt":31},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[110]]