[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DRY76TP1X5DS4XK2DYB1NQ":3,"skill-same:01M6DRY76TP1X5DS4XK2DYB1NQ":81},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M6DRY76TP1X5DS4XK2DYB1NQ","challenge",null,"\u002Fem -challenge — Pre-Mortem Plan Analysis","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fchallenge\u002FSKILL.md",[],[5,19,20],"analysis","plan","2026-11-10 10:12:30",false,"---\nname: \"challenge\"\ndescription: \"\u002Fem -challenge — Pre-Mortem Plan Analysis\"\n---\n\n# \u002Fem:challenge — Pre-Mortem Plan Analysis\n\n**Command:** `\u002Fem:challenge \u003Cplan>`\n\nSystematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality.\n\n---\n\n## The Core Idea\n\nMost plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world.\n\nThe pre-mortem technique: **imagine it's 12 months from now and this plan failed spectacularly. Now work backwards. Why?**\n\nThat's not pessimism. It's how you build something that doesn't collapse.\n\n---\n\n## When to Run a Challenge\n\n- Before committing significant resources to a plan\n- Before presenting to the board or investors\n- When you notice you're only hearing positive feedback about the plan\n- When the plan requires multiple external dependencies to align\n- When there's pressure to move fast and \"figure it out later\"\n- When you feel excited about the plan (excitement is a signal to scrutinize harder)\n\n---\n\n## The Challenge Framework\n\n### Step 1: Extract Core Assumptions\nBefore you can test a plan, you need to surface everything it assumes to be true.\n\nFor each section of the plan, ask:\n- What has to be true for this to work?\n- What are we assuming about customer behavior?\n- What are we assuming about competitor response?\n- What are we assuming about our own execution capability?\n- What external factors does this depend on?\n\n**Common assumption categories:**\n- **Market assumptions** — size, growth rate, customer willingness to pay, buying cycle\n- **Execution assumptions** — team capacity, velocity, no major hires needed\n- **Customer assumptions** — they have the problem, they know they have it, they'll pay to solve it\n- **Competitive assumptions** — incumbents won't respond, no new entrant, moat holds\n- **Financial assumptions** — burn rate, revenue timing, CAC, LTV ratios\n- **Dependency assumptions** — partner will deliver, API won't change, regulations won't shift\n\n### Step 2: Rate Each Assumption\n\nFor every assumption extracted, rate it on two dimensions:\n\n**Confidence level (how sure are you this is true):**\n- **High** — verified with data, customer conversations, market research\n- **Medium** — directionally right but not validated\n- **Low** — plausible but untested\n- **Unknown** — we simply don't know\n\n**Impact if wrong (what happens if this assumption fails):**\n- **Critical** — plan fails entirely\n- **High** — major delay or cost overrun\n- **Medium** — significant rework required\n- **Low** — manageable adjustment\n\n### Step 3: Map Vulnerabilities\n\nThe matrix of Low\u002FUnknown confidence × Critical\u002FHigh impact = your highest-risk assumptions.\n\n**Vulnerability = Low confidence + High impact**\n\nThese are not problems to ignore. They're the bets you're making. The question is: are you making them consciously?\n\n### Step 4: Find the Dependency Chain\n\nMany plans fail not because any single assumption is wrong, but because multiple assumptions have to be right simultaneously.\n\nMap the chain:\n- Does assumption B depend on assumption A being true first?\n- If the first thing goes wrong, how many downstream things break?\n- What's the critical path? What has zero slack?\n\n### Step 5: Test the Reversibility\n\nFor each critical vulnerability: if this assumption turns out to be wrong at month 3, what do you do?\n\n- Can you pivot?\n- Can you cut scope?\n- Is money already spent?\n- Are commitments already made?\n\nThe less reversible, the more rigorously you need to validate before committing.\n\n---\n\n## Output Format\n\n**Challenge Report: [Plan Name]**\n\n```\nCORE ASSUMPTIONS (extracted)\n1. [Assumption] — Confidence: [H\u002FM\u002FL\u002F?] — Impact if wrong: [Critical\u002FHigh\u002FMedium\u002FLow]\n2. ...\n\nVULNERABILITY MAP\nCritical risks (act before proceeding):\n• [#N] [Assumption] — WHY it might be wrong — WHAT breaks if it is\n\nHigh risks (validate before scaling):\n• ...\n\nDEPENDENCY CHAIN\n[Assumption A] → depends on → [Assumption B] → which enables → [Assumption C]\nWeakest link: [X] — if this breaks, [Y] and [Z] also fail\n\nREVERSIBILITY ASSESSMENT\n• Reversible bets: [list]\n• Irreversible commitments: [list — treat with extreme care]\n\nKILL SWITCHES\nWhat would have to be true at [30\u002F60\u002F90 days] to continue vs. kill\u002Fpivot?\n• Continue if: ...\n• Kill\u002Fpivot if: ...\n\nHARDENING ACTIONS\n1. [Specific validation to do before proceeding]\n2. [Alternative approach to consider]\n3. [Contingency to build into the plan]\n```\n\n---\n\n## Challenge Patterns by Plan Type\n\n### Product Roadmap\n- Are we building what customers will pay for, or what they said they wanted?\n- Does the velocity estimate account for real team capacity (not theoretical)?\n- What happens if the anchor feature takes 3× longer than estimated?\n- Who owns decisions when requirements conflict?\n\n### Go-to-Market Plan\n- What's the actual ICP conversion rate, not the hoped-for one?\n- How many touches to close, and do you have the sales capacity for that?\n- What happens if the first 10 deals take 3 months instead of 1?\n- Is \"land and expand\" a real motion or a hope?\n\n### Hiring Plan\n- What happens if the key hire takes 4 months to find, not 6 weeks?\n- Is the plan dependent on retaining specific people who might leave?\n- Does the plan account for ramp time (usually 3–6 months before full productivity)?\n- What's the burn impact if headcount leads revenue by 6 months?\n\n### Fundraising Plan\n- What's your fallback if the lead investor passes?\n- Have you modeled the timeline if it takes 6 months, not 3?\n- What's your runway at current burn if the round closes at the low end?\n- What assumptions break if you raise 50% of the target amount?\n\n---\n\n## The Hardest Questions\n\nThese are the ones people skip:\n- \"What's the bear case, not the base case?\"\n- \"If this exact plan was run by a team we don't trust, would it work?\"\n- \"What are we not saying out loud because it's uncomfortable?\"\n- \"Who has incentives to make this plan sound better than it is?\"\n- \"What would an enemy of this plan attack first?\"\n\n---\n\n## Deliverable\n\nThe output of `\u002Fem:challenge` is not permission to stop. It's a vulnerability map. Now you can make conscious decisions: validate the risky assumptions, hedge the critical ones, or accept the bets you're making knowingly.\n\nUnknown risks are dangerous. Known risks are manageable.\n","# \u002Fem:challenge — Pre-Mortem Plan Analysis\n\n**Command:** `\u002Fem:challenge \u003Cplan>`\n\nSystematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality.\n\n---\n\n## The Core Idea\n\nMost plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world.\n\nThe pre-mortem technique: **imagine it's 12 months from now and this plan failed spectacularly. Now work backwards. Why?**\n\nThat's not pessimism. It's how you build something that doesn't collapse.\n\n---\n\n## When to Run a Challenge\n\n- Before committing significant resources to a plan\n- Before presenting to the board or investors\n- When you notice you're only hearing positive feedback about the plan\n- When the plan requires multiple external dependencies to align\n- When there's pressure to move fast and \"figure it out later\"\n- When you feel excited about the plan (excitement is a signal to scrutinize harder)\n\n---\n\n## The Challenge Framework\n\n### Step 1: Extract Core Assumptions\nBefore you can test a plan, you need to surface everything it assumes to be true.\n\nFor each section of the plan, ask:\n- What has to be true for this to work?\n- What are we assuming about customer behavior?\n- What are we assuming about competitor response?\n- What are we assuming about our own execution capability?\n- What external factors does this depend on?\n\n**Common assumption categories:**\n- **Market assumptions** — size, growth rate, customer willingness to pay, buying cycle\n- **Execution assumptions** — team capacity, velocity, no major hires needed\n- **Customer assumptions** — they have the problem, they know they have it, they'll pay to solve it\n- **Competitive assumptions** — incumbents won't respond, no new entrant, moat holds\n- **Financial assumptions** — burn rate, revenue timing, CAC, LTV ratios\n- **Dependency assumptions** — partner will deliver, API won't change, regulations won't shift\n\n### Step 2: Rate Each Assumption\n\nFor every assumption extracted, rate it on two dimensions:\n\n**Confidence level (how sure are you this is true):**\n- **High** — verified with data, customer conversations, market research\n- **Medium** — directionally right but not validated\n- **Low** — plausible but untested\n- **Unknown** — we simply don't know\n\n**Impact if wrong (what happens if this assumption fails):**\n- **Critical** — plan fails entirely\n- **High** — major delay or cost overrun\n- **Medium** — significant rework required\n- **Low** — manageable adjustment\n\n### Step 3: Map Vulnerabilities\n\nThe matrix of Low\u002FUnknown confidence × Critical\u002FHigh impact = your highest-risk assumptions.\n\n**Vulnerability = Low confidence + High impact**\n\nThese are not problems to ignore. They're the bets you're making. The question is: are you making them consciously?\n\n### Step 4: Find the Dependency Chain\n\nMany plans fail not because any single assumption is wrong, but because multiple assumptions have to be right simultaneously.\n\nMap the chain:\n- Does assumption B depend on assumption A being true first?\n- If the first thing goes wrong, how many downstream things break?\n- What's the critical path? What has zero slack?\n\n### Step 5: Test the Reversibility\n\nFor each critical vulnerability: if this assumption turns out to be wrong at month 3, what do you do?\n\n- Can you pivot?\n- Can you cut scope?\n- Is money already spent?\n- Are commitments already made?\n\nThe less reversible, the more rigorously you need to validate before committing.\n\n---\n\n## Output Format\n\n**Challenge Report: [Plan Name]**\n\n```\nCORE ASSUMPTIONS (extracted)\n1. [Assumption] — Confidence: [H\u002FM\u002FL\u002F?] — Impact if wrong: [Critical\u002FHigh\u002FMedium\u002FLow]\n2. ...\n\nVULNERABILITY MAP\nCritical risks (act before proceeding):\n• [#N] [Assumption] — WHY it might be wrong — WHAT breaks if it is\n\nHigh risks (validate before scaling):\n• ...\n\nDEPENDENCY CHAIN\n[Assumption A] → depends on → [Assumption B] → which enables → [Assumption C]\nWeakest link: [X] — if this breaks, [Y] and [Z] also fail\n\nREVERSIBILITY ASSESSMENT\n• Reversible bets: [list]\n• Irreversible commitments: [list — treat with extreme care]\n\nKILL SWITCHES\nWhat would have to be true at [30\u002F60\u002F90 days] to continue vs. kill\u002Fpivot?\n• Continue if: ...\n• Kill\u002Fpivot if: ...\n\nHARDENING ACTIONS\n1. [Specific validation to do before proceeding]\n2. [Alternative approach to consider]\n3. [Contingency to build into the plan]\n```\n\n---\n\n## Challenge Patterns by Plan Type\n\n### Product Roadmap\n- Are we building what customers will pay for, or what they said they wanted?\n- Does the velocity estimate account for real team capacity (not theoretical)?\n- What happens if the anchor feature takes 3× longer than estimated?\n- Who owns decisions when requirements conflict?\n\n### Go-to-Market Plan\n- What's the actual ICP conversion rate, not the hoped-for one?\n- How many touches to close, and do you have the sales capacity for that?\n- What happens if the first 10 deals take 3 months instead of 1?\n- Is \"land and expand\" a real motion or a hope?\n\n### Hiring Plan\n- What happens if the key hire takes 4 months to find, not 6 weeks?\n- Is the plan dependent on retaining specific people who might leave?\n- Does the plan account for ramp time (usually 3–6 months before full productivity)?\n- What's the burn impact if headcount leads revenue by 6 months?\n\n### Fundraising Plan\n- What's your fallback if the lead investor passes?\n- Have you modeled the timeline if it takes 6 months, not 3?\n- What's your runway at current burn if the round closes at the low end?\n- What assumptions break if you raise 50% of the target amount?\n\n---\n\n## The Hardest Questions\n\nThese are the ones people skip:\n- \"What's the bear case, not the base case?\"\n- \"If this exact plan was run by a team we don't trust, would it work?\"\n- \"What are we not saying out loud because it's uncomfortable?\"\n- \"Who has incentives to make this plan sound better than it is?\"\n- \"What would an enemy of this plan attack first?\"\n\n---\n\n## Deliverable\n\nThe output of `\u002Fem:challenge` is not permission to stop. It's a vulnerability map. Now you can make conscious decisions: validate the risky assumptions, hedge the critical ones, or accept the bets you're making knowingly.\n\nUnknown risks are dangerous. Known risks are manageable.\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","c-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fchallenge",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill challenge",{"tool":39,"command":40},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill challenge",{"tool":42,"command":43},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill challenge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fchallenge\u002FSKILL.md",true,[47,53,57,61,65,69,73,77],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"algorithms.md","REFERENCE","参考文档",97,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Falgorithms.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"failure_modes.md",100,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Ffailure_modes.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"formulas.md",95,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Fformulas.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"implementation_notes.md",107,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Fimplementation_notes.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"integration_arbitragex.md",109,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Fintegration_arbitragex.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"manifest.json",863,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Fmanifest.json",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references.json",287,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Freferences.json",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"validation_tests.md",103,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdynamic-token-universe-selection\u002Fvalidation_tests.md",[82,108,133,164,184,207],{"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":21},"01M6DSNYM8PZKEXGYMRX53PVPH","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[89,90,91,92,93,94,95,96,97,98,19,99,100,101,102,103,104,105,106,107],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","user","use","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":21},"01M6DSNSRBGVZWS23TK0ZQ52QC","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[115,116,117,118,119,120,121,122,20,123,124,125,126,127,128,129,130,131,106,132],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":149,"publishedAt":21},"01M6DSNN7GNR2HZE66S4D31EP8","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[139,144],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[150,151,152,153,154,155,118,156,157,158,159,160,100,116,161,162,163,104,105,106],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":21},"01M6DSNE5PQM106PM4EDGPBWGZ","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000037","律师与法务",[174,151,153,175,176,177,178,158,179,159,91,180,116,181,182,183,105],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":194,"publishedAt":21},"01M6DSN7MYXB6X42TB1GH2TNSB","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\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":171,"categoryName":172,"taxonomyType":147,"taxonomyTypeDesc":148},[118,195,151,153,196,197,156,98,198,159,199,200,100,201,202,203,106,204,205,206],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"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":213,"publishedAt":21},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[156,214,215,121,216,217,218,219,91,100,220,103,105,106],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]