[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBVNXABF85HKMG56R9ZCGA":3,"skill-same:01M6KBVNXABF85HKMG56R9ZCGA":76},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6KBVNXABF85HKMG56R9ZCGA","product-discovery",null,"Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fproduct-discovery\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],"product","discovery","product discovery","testing","planning","use","delivery","fit","problem","mapping","resources","sprints","problem-solution","2026-11-10 10:12:30",false,"---\nname: product-discovery\ndescription: Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.\n---\n\n# Product Discovery\n\nRun structured discovery to identify high-value opportunities and de-risk product bets.\n\n## When To Use\n\nUse this skill for:\n- Opportunity Solution Tree facilitation\n- Assumption mapping and test planning\n- Problem validation interviews and evidence synthesis\n- Solution validation with prototypes\u002Fexperiments\n- Discovery sprint planning and outputs\n\n## Core Discovery Workflow\n\n1. Define desired outcome\n- Set one measurable outcome to improve.\n- Establish baseline and target horizon.\n\n2. Build Opportunity Solution Tree (OST)\n- Outcome -> opportunities -> solution ideas -> experiments\n- Keep opportunities grounded in user evidence, not internal opinions.\n\n3. Map assumptions\n- Identify desirability, viability, feasibility, and usability assumptions.\n- Score assumptions by risk and certainty.\n\nUse:\n```bash\npython3 scripts\u002Fassumption_mapper.py assumptions.csv\n```\n\n4. Validate the problem\n- Conduct interviews and behavior analysis.\n- Confirm frequency, severity, and willingness to solve.\n- Reject weak opportunities early.\n\n5. Validate the solution\n- Prototype before building.\n- Run concept, usability, and value tests.\n- Measure behavior, not only stated preference.\n\n6. Plan discovery sprint\n- 1-2 week cycle with explicit hypotheses\n- Daily evidence reviews\n- End with decision: proceed, pivot, or stop\n\n## Opportunity Solution Tree (Teresa Torres)\n\nStructure:\n- Outcome: metric you want to move\n- Opportunities: unmet customer needs\u002Fpains\n- Solutions: candidate interventions\n- Experiments: fastest learning actions\n\nQuality checks:\n- At least 3 distinct opportunities before converging.\n- At least 2 experiments per top opportunity.\n- Tie every branch to evidence source.\n\n## Assumption Mapping\n\nAssumption categories:\n- Desirability: users want this\n- Viability: business value exists\n- Feasibility: team can build\u002Foperate it\n- Usability: users can successfully use it\n\nPrioritization rule:\n- High risk + low certainty assumptions are tested first.\n\n## Problem Validation Techniques\n\n- Problem interviews focused on current behavior\n- Journey friction mapping\n- Support ticket and sales-call synthesis\n- Behavioral analytics triangulation\n\nEvidence threshold examples:\n- Same pain repeated across multiple target users\n- Observable workaround behavior\n- Measurable cost of current pain\n\n## Solution Validation Techniques\n\n- Concept tests (value proposition comprehension)\n- Prototype usability tests (task success\u002Ftime-to-complete)\n- Fake door or concierge tests (demand signal)\n- Limited beta cohorts (retention\u002Factivation signals)\n\n## Discovery Sprint Planning\n\nSuggested 10-day structure:\n- Day 1-2: Outcome + opportunity framing\n- Day 3-4: Assumption mapping + test design\n- Day 5-7: Problem and solution tests\n- Day 8-9: Evidence synthesis + decision options\n- Day 10: Stakeholder decision review\n\n## Tooling\n\n### `scripts\u002Fassumption_mapper.py`\n\nCLI utility that:\n- reads assumptions from CSV or inline input\n- scores risk\u002Fcertainty priority\n- emits prioritized test plan with suggested test types\n\nSee `references\u002Fdiscovery-frameworks.md` for framework details.\n","# Product Discovery\n\nRun structured discovery to identify high-value opportunities and de-risk product bets.\n\n## When To Use\n\nUse this skill for:\n- Opportunity Solution Tree facilitation\n- Assumption mapping and test planning\n- Problem validation interviews and evidence synthesis\n- Solution validation with prototypes\u002Fexperiments\n- Discovery sprint planning and outputs\n\n## Core Discovery Workflow\n\n1. Define desired outcome\n- Set one measurable outcome to improve.\n- Establish baseline and target horizon.\n\n2. Build Opportunity Solution Tree (OST)\n- Outcome -> opportunities -> solution ideas -> experiments\n- Keep opportunities grounded in user evidence, not internal opinions.\n\n3. Map assumptions\n- Identify desirability, viability, feasibility, and usability assumptions.\n- Score assumptions by risk and certainty.\n\nUse:\n```bash\npython3 scripts\u002Fassumption_mapper.py assumptions.csv\n```\n\n4. Validate the problem\n- Conduct interviews and behavior analysis.\n- Confirm frequency, severity, and willingness to solve.\n- Reject weak opportunities early.\n\n5. Validate the solution\n- Prototype before building.\n- Run concept, usability, and value tests.\n- Measure behavior, not only stated preference.\n\n6. Plan discovery sprint\n- 1-2 week cycle with explicit hypotheses\n- Daily evidence reviews\n- End with decision: proceed, pivot, or stop\n\n## Opportunity Solution Tree (Teresa Torres)\n\nStructure:\n- Outcome: metric you want to move\n- Opportunities: unmet customer needs\u002Fpains\n- Solutions: candidate interventions\n- Experiments: fastest learning actions\n\nQuality checks:\n- At least 3 distinct opportunities before converging.\n- At least 2 experiments per top opportunity.\n- Tie every branch to evidence source.\n\n## Assumption Mapping\n\nAssumption categories:\n- Desirability: users want this\n- Viability: business value exists\n- Feasibility: team can build\u002Foperate it\n- Usability: users can successfully use it\n\nPrioritization rule:\n- High risk + low certainty assumptions are tested first.\n\n## Problem Validation Techniques\n\n- Problem interviews focused on current behavior\n- Journey friction mapping\n- Support ticket and sales-call synthesis\n- Behavioral analytics triangulation\n\nEvidence threshold examples:\n- Same pain repeated across multiple target users\n- Observable workaround behavior\n- Measurable cost of current pain\n\n## Solution Validation Techniques\n\n- Concept tests (value proposition comprehension)\n- Prototype usability tests (task success\u002Ftime-to-complete)\n- Fake door or concierge tests (demand signal)\n- Limited beta cohorts (retention\u002Factivation signals)\n\n## Discovery Sprint Planning\n\nSuggested 10-day structure:\n- Day 1-2: Outcome + opportunity framing\n- Day 3-4: Assumption mapping + test design\n- Day 5-7: Problem and solution tests\n- Day 8-9: Evidence synthesis + decision options\n- Day 10: Stakeholder decision review\n\n## Tooling\n\n### `scripts\u002Fassumption_mapper.py`\n\nCLI utility that:\n- reads assumptions from CSV or inline input\n- scores risk\u002Fcertainty priority\n- emits prioritized test plan with suggested test types\n\nSee `references\u002Fdiscovery-frameworks.md` for framework details.\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","product-team\u002Fproduct-discovery",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill product-discovery",{"tool":56,"command":57},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill product-discovery",{"tool":59,"command":60},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill product-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fproduct-discovery\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fdiscovery-frameworks.md","REFERENCE","参考文档",1849,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fproduct-discovery\u002Freferences\u002Fdiscovery-frameworks.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fassumption_mapper.py","SCRIPT","脚本",4062,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fproduct-discovery\u002Fscripts\u002Fassumption_mapper.py",[77,106,130,155,187,207],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":86,"publishedAt":37},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[87,88,89,90,91,92,93,94,29,95,96,97,98,99,100,101,102,103,104,105],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"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":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":37},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[113,114,115,116,117,24,118,119,94,29,120,121,122,123,124,125,126,127,128,129],"risk","risk management specialist","management","risk management","risk evaluation","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"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":37},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,29,146,147,148,149,150,151,152,153,154,105],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":169,"publishedAt":37},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[161,166],{"categoryNo":162,"categoryName":163,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[170,171,154,172,173,174,175,176,177,29,178,179,180,181,182,183,184,185,105,186],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":37},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[193],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},[195,171,154,196,197,198,199,200,87,201,177,202,138,203,204,205,121,182,105,206],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":220,"publishedAt":37},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[213,216,219],{"categoryNo":214,"categoryName":215,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":217,"categoryName":218,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},[221,222,171,154,196,223,224,91,177,225,226,227,228,229,122,230,231,232,233,105],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]