[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HQ5BHSC6PC57203FR18PN":3,"skill-same:01M70HQ5BHSC6PC57203FR18PN":88},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M70HQ5BHSC6PC57203FR18PN","requirements-analysis",null,"Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs\u002Fspecs\u002F. Includes validation checklist, iterative cycle pattern, and multi-angle review process.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"analysis","requirements","requirements analysis","Product Requirements","user stories","analyzing","pattern","edit","write","read","product","create","review process","review","when","documents","acceptance","writing","files","cycle","2026-11-10 10:12:30",false,"---\nname: requirements-analysis\ndescription: Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs\u002Fspecs\u002F. Includes validation checklist, iterative cycle pattern, and multi-angle review process.\nallowed-tools: Read, Write, Edit, Task, TodoWrite, Grep, Glob\n---\n\n# Product Requirements Skill\n\nYou are a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Create a new PRD** from the template\n- **Complete sections** in an existing product-requirements.md\n- **Validate PRD completeness** and quality\n- **Review requirements** from multiple perspectives\n- **Work on any `product-requirements.md`** file in docs\u002Fspecs\u002F\n\n## Template\n\nThe PRD template is at [template.md](template.md). Use this structure exactly.\n\n**To write template to spec directory:**\n1. Read the template: `plugins\u002Fstart\u002Fskills\u002Fproduct-requirements\u002Ftemplate.md`\n2. Write to spec directory: `docs\u002Fspecs\u002F[ID]-[name]\u002Fproduct-requirements.md`\n\n## PRD Focus Areas\n\nWhen working on a PRD, focus on:\n- **WHAT** needs to be built (features, capabilities)\n- **WHY** it matters (problem, value proposition)\n- **WHO** uses it (personas, journeys)\n- **WHEN** it succeeds (metrics, acceptance criteria)\n\n**Avoid:**\n- Technical implementation details\n- Architecture decisions\n- Database schemas\n- API specifications\n\nThese belong in the Solution Design Document (SDD).\n\n## Cycle Pattern\n\nFor each section requiring clarification, follow this iterative process:\n\n### 1. Discovery Phase\n- **Identify ALL activities needed** based on missing information\n- **Launch parallel specialist agents** to investigate:\n  - Market analysis for competitive landscape\n  - User research for personas and journeys\n  - Requirements clarification for edge cases\n- Consider relevant research areas, best practices, success criteria\n\n### 2. Documentation Phase\n- **Update the PRD** with research findings\n- **Replace [NEEDS CLARIFICATION] markers** with actual content\n- Focus only on current section being processed\n- Follow template structure exactly - never add or remove sections\n\n### 3. Review Phase\n- **Present ALL agent findings** to user (complete responses, not summaries)\n- Show conflicting information or recommendations\n- Present proposed content based on research\n- Highlight questions needing user clarification\n- **Wait for user confirmation** before next cycle\n\n**Ask yourself each cycle:**\n1. Have I identified ALL activities needed for this section?\n2. Have I launched parallel specialist agents to investigate?\n3. Have I updated the PRD according to findings?\n4. Have I presented COMPLETE agent responses to the user?\n5. Have I received user confirmation before proceeding?\n\n## Multi-Angle Final Validation\n\nBefore completing the PRD, validate from multiple perspectives:\n\n### Context Review\nLaunch specialists to verify:\n- Problem statement clarity - is it specific and measurable?\n- User persona completeness - do we understand our users?\n- Value proposition strength - is it compelling?\n\n### Gap Analysis\nLaunch specialists to identify:\n- Gaps in user journeys\n- Missing edge cases\n- Unclear acceptance criteria\n- Contradictions between sections\n\n### User Input\nBased on gaps found:\n- Formulate specific questions using AskUserQuestion\n- Probe alternative scenarios\n- Validate priority trade-offs\n- Confirm success criteria\n\n### Coherence Validation\nLaunch specialists to confirm:\n- Requirements completeness\n- Feasibility assessment\n- Alignment with stated goals\n- Edge case coverage\n\n## Validation Checklist\n\nSee [validation.md](validation.md) for the complete checklist. Key gates:\n\n- [ ] All required sections are complete\n- [ ] No [NEEDS CLARIFICATION] markers remain\n- [ ] Problem statement is specific and measurable\n- [ ] Problem is validated by evidence (not assumptions)\n- [ ] Context → Problem → Solution flow makes sense\n- [ ] Every persona has at least one user journey\n- [ ] All MoSCoW categories addressed (Must\u002FShould\u002FCould\u002FWon't)\n- [ ] Every feature has testable acceptance criteria\n- [ ] Every metric has corresponding tracking events\n- [ ] No feature redundancy (check for duplicates)\n- [ ] No contradictions between sections\n- [ ] No technical implementation details included\n- [ ] A new team member could understand this PRD\n\n## Output Format\n\nAfter PRD work, report:\n\n```\n📝 PRD Status: [spec-id]-[name]\n\nSections Completed:\n- [Section 1]: ✅ Complete\n- [Section 2]: ⚠️ Needs user input on [topic]\n- [Section 3]: 🔄 In progress\n\nValidation Status:\n- [X] items passed\n- [Y] items pending\n\nNext Steps:\n- [What needs to happen next]\n```\n\n## Examples\n\nSee [examples\u002Fgood-prd.md](examples\u002Fgood-prd.md) for reference on well-structured PRDs.\n","# Product Requirements Skill\n\nYou are a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Create a new PRD** from the template\n- **Complete sections** in an existing product-requirements.md\n- **Validate PRD completeness** and quality\n- **Review requirements** from multiple perspectives\n- **Work on any `product-requirements.md`** file in docs\u002Fspecs\u002F\n\n## Template\n\nThe PRD template is at [template.md](template.md). Use this structure exactly.\n\n**To write template to spec directory:**\n1. Read the template: `plugins\u002Fstart\u002Fskills\u002Fproduct-requirements\u002Ftemplate.md`\n2. Write to spec directory: `docs\u002Fspecs\u002F[ID]-[name]\u002Fproduct-requirements.md`\n\n## PRD Focus Areas\n\nWhen working on a PRD, focus on:\n- **WHAT** needs to be built (features, capabilities)\n- **WHY** it matters (problem, value proposition)\n- **WHO** uses it (personas, journeys)\n- **WHEN** it succeeds (metrics, acceptance criteria)\n\n**Avoid:**\n- Technical implementation details\n- Architecture decisions\n- Database schemas\n- API specifications\n\nThese belong in the Solution Design Document (SDD).\n\n## Cycle Pattern\n\nFor each section requiring clarification, follow this iterative process:\n\n### 1. Discovery Phase\n- **Identify ALL activities needed** based on missing information\n- **Launch parallel specialist agents** to investigate:\n  - Market analysis for competitive landscape\n  - User research for personas and journeys\n  - Requirements clarification for edge cases\n- Consider relevant research areas, best practices, success criteria\n\n### 2. Documentation Phase\n- **Update the PRD** with research findings\n- **Replace [NEEDS CLARIFICATION] markers** with actual content\n- Focus only on current section being processed\n- Follow template structure exactly - never add or remove sections\n\n### 3. Review Phase\n- **Present ALL agent findings** to user (complete responses, not summaries)\n- Show conflicting information or recommendations\n- Present proposed content based on research\n- Highlight questions needing user clarification\n- **Wait for user confirmation** before next cycle\n\n**Ask yourself each cycle:**\n1. Have I identified ALL activities needed for this section?\n2. Have I launched parallel specialist agents to investigate?\n3. Have I updated the PRD according to findings?\n4. Have I presented COMPLETE agent responses to the user?\n5. Have I received user confirmation before proceeding?\n\n## Multi-Angle Final Validation\n\nBefore completing the PRD, validate from multiple perspectives:\n\n### Context Review\nLaunch specialists to verify:\n- Problem statement clarity - is it specific and measurable?\n- User persona completeness - do we understand our users?\n- Value proposition strength - is it compelling?\n\n### Gap Analysis\nLaunch specialists to identify:\n- Gaps in user journeys\n- Missing edge cases\n- Unclear acceptance criteria\n- Contradictions between sections\n\n### User Input\nBased on gaps found:\n- Formulate specific questions using AskUserQuestion\n- Probe alternative scenarios\n- Validate priority trade-offs\n- Confirm success criteria\n\n### Coherence Validation\nLaunch specialists to confirm:\n- Requirements completeness\n- Feasibility assessment\n- Alignment with stated goals\n- Edge case coverage\n\n## Validation Checklist\n\nSee [validation.md](validation.md) for the complete checklist. Key gates:\n\n- [ ] All required sections are complete\n- [ ] No [NEEDS CLARIFICATION] markers remain\n- [ ] Problem statement is specific and measurable\n- [ ] Problem is validated by evidence (not assumptions)\n- [ ] Context → Problem → Solution flow makes sense\n- [ ] Every persona has at least one user journey\n- [ ] All MoSCoW categories addressed (Must\u002FShould\u002FCould\u002FWon't)\n- [ ] Every feature has testable acceptance criteria\n- [ ] Every metric has corresponding tracking events\n- [ ] No feature redundancy (check for duplicates)\n- [ ] No contradictions between sections\n- [ ] No technical implementation details included\n- [ ] A new team member could understand this PRD\n\n## Output Format\n\nAfter PRD work, report:\n\n```\n📝 PRD Status: [spec-id]-[name]\n\nSections Completed:\n- [Section 1]: ✅ Complete\n- [Section 2]: ⚠️ Needs user input on [topic]\n- [Section 3]: 🔄 In progress\n\nValidation Status:\n- [X] items passed\n- [Y] items pending\n\nNext Steps:\n- [What needs to happen next]\n```\n\n## Examples\n\nSee [examples\u002Fgood-prd.md](examples\u002Fgood-prd.md) for reference on well-structured PRDs.\n",{"name":5,"description":7,"allowed-tools":49},"Read, Write, Edit, Task, TodoWrite, Grep, Glob","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-analysis",{"tool":66,"command":67},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-analysis",{"tool":69,"command":70},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill requirements-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis\u002FSKILL.md",true,[74,80,84],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"examples\u002Fgood-prd.md","REFERENCE","参考文档",3090,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis\u002Fexamples\u002Fgood-prd.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"template.md",5576,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis\u002Ftemplate.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"validation.md",3093,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Frequirements-analysis\u002Fvalidation.md",[89,98,106,114,122,130],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":97},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":97},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":97},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":97},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":97},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]