[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DRYF6Z6FK3K2XK3SQ2R8BS":3,"skill-same:01M6DRYF6Z6FK3K2XK3SQ2R8BS":55},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6DRYF6Z6FK3K2XK3SQ2R8BS","stress-test",null,"\u002Fem -stress-test — Business Assumption Stress Testing","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\u002Fstress-test\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,5],"test","stress test","testing","stress testing","business","2026-11-10 10:12:30",false,"---\nname: \"stress-test\"\ndescription: \"\u002Fem -stress-test — Business Assumption Stress Testing\"\n---\n\n# \u002Fem:stress-test — Business Assumption Stress Testing\n\n**Command:** `\u002Fem:stress-test \u003Cassumption>`\n\nTake any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention.\n\n---\n\n## Why Most Assumptions Are Wrong\n\nFounders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started.\n\n**The most dangerous assumptions are the ones everyone agrees on.**\n\nWhen the whole team believes the $50M market is real, when every investor call goes well so you assume the round will close, when your model shows $2M ARR by December and nobody questions it — that's when you're most exposed.\n\nStress testing isn't pessimism. It's calibration.\n\n---\n\n## The Stress-Test Methodology\n\n### Step 1: Isolate the Assumption\n\nState it explicitly. Not \"our market is large\" but \"the total addressable market for B2B spend management software in German SMEs is €2.3B.\"\n\nThe more specific the assumption, the more testable it is. Vague assumptions are unfalsifiable — and therefore useless.\n\n**Common assumption types:**\n- **Market size** — TAM, SAM, SOM; growth rate; customer segments\n- **Customer behavior** — willingness to pay, churn, expansion, referrals\n- **Revenue model** — conversion rates, deal size, sales cycle, CAC\n- **Competitive position** — moat durability, competitor response speed, switching cost\n- **Execution** — team velocity, hire timeline, product timeline, operational scaling\n- **Macro** — regulatory environment, economic conditions, technology availability\n\n### Step 2: Find the Counter-Evidence\n\nFor every assumption, actively search for evidence that it's wrong.\n\nAsk:\n- Who has tried this and failed?\n- What data contradicts this assumption?\n- What does the bear case look like?\n- If a smart skeptic was looking at this, what would they point to?\n- What's the base rate for assumptions like this?\n\n**Sources of counter-evidence:**\n- Comparable companies that failed in adjacent markets\n- Customer churn data from similar businesses\n- Historical accuracy of similar forecasts\n- Industry reports with conflicting data\n- What competitors who tried this found\n\nThe goal isn't to find a reason to stop — it's to surface what you don't know.\n\n### Step 3: Model the Downside\n\nMost plans model the base case and the upside. Stress testing means modeling the downside explicitly.\n\n**For quantitative assumptions (revenue, growth, conversion):**\n\n| Scenario | Assumption Value | Probability | Impact |\n|----------|-----------------|-------------|--------|\n| Base case | [Original value] | ? | |\n| Bear case | -30% | ? | |\n| Stress case | -50% | ? | |\n| Catastrophic | -80% | ? | |\n\nKey question at each level: **Does the business survive? Does the plan make sense?**\n\n**For qualitative assumptions (moat, product-market fit, team capability):**\n\n- What's the earliest signal this assumption is wrong?\n- How long would it take you to notice?\n- What happens between when it breaks and when you detect it?\n\n### Step 4: Calculate Sensitivity\n\nSome assumptions matter more than others. Sensitivity analysis answers: **if this one assumption changes, how much does the outcome change?**\n\nExample: \n- If CAC doubles, how does that change runway?\n- If churn goes from 5% to 10%, how does that change NRR in 24 months?\n- If the deal cycle is 6 months instead of 3, how does that affect Q3 revenue?\n\nHigh sensitivity = the assumption is a key lever. Wrong = big problem.\n\n### Step 5: Propose the Hedge\n\nFor every high-risk assumption, there should be a hedge:\n\n- **Validation hedge** — test it before betting on it (pilot, customer conversation, small experiment)\n- **Contingency hedge** — if it's wrong, what's plan B?\n- **Early warning hedge** — what's the leading indicator that would tell you it's breaking before it's too late to act?\n\n---\n\n## Stress Test Patterns by Assumption Type\n\n### Revenue Projections\n\n**Common failures:**\n- Bottom-up model assumes 100% of pipeline converts\n- Doesn't account for deal slippage, churn, seasonality\n- New channel assumed to work before tested at scale\n\n**Stress questions:**\n- What's your actual historical win rate on pipeline?\n- If your top 3 deals slip to next quarter, what happens to the number?\n- What's the model look like if your new sales rep takes 4 months to ramp, not 2?\n- If expansion revenue doesn't materialize, what's the growth rate?\n\n**Test:** Build the revenue model from historical win rates, not hoped-for ones.\n\n### Market Size\n\n**Common failures:**\n- TAM calculated top-down from industry reports without bottoms-up validation\n- Conflating total market with serviceable market\n- Assuming 100% of SAM is reachable\n\n**Stress questions:**\n- How many companies in your ICP actually exist and can you name them?\n- What's your serviceable obtainable market in year 1-3?\n- What percentage of your ICP is currently spending on any solution to this problem?\n- What does \"winning\" look like and what market share does that require?\n\n**Test:** Build a list of target accounts. Count them. Multiply by ACV. That's your SAM.\n\n### Competitive Moat\n\n**Common failures:**\n- Moat is technology advantage that can be built in 6 months\n- Network effects that haven't yet materialized\n- Data advantage that requires scale you don't have\n\n**Stress questions:**\n- If a well-funded competitor copied your best feature in 90 days, what do customers do?\n- What's your retention rate among customers who have tried alternatives?\n- Is the moat real today or theoretical at scale?\n- What would it cost a competitor to reach feature parity?\n\n**Test:** Ask churned customers why they left and whether a competitor could have kept them.\n\n### Hiring Plan\n\n**Common failures:**\n- Time-to-hire assumes standard recruiting cycle, not current market\n- Ramp time not modeled (3-6 months before full productivity)\n- Key hire dependency: plan only works if specific person is hired\n\n**Stress questions:**\n- What happens if the VP Sales hire takes 5 months, not 2?\n- What does execution look like if you only hire 70% of planned headcount?\n- Which single person, if they left tomorrow, would most damage the plan?\n- Is the plan achievable with current team if hiring freezes?\n\n**Test:** Model the plan with 0 net new hires. What still works?\n\n### Competitive Response\n\n**Common failures:**\n- Assumes incumbents won't respond (they will if you're winning)\n- Underestimates speed of response\n- Doesn't model resource asymmetry\n\n**Stress questions:**\n- If the market leader copies your product in 6 months, how does pricing change?\n- What's your response if a competitor raises $30M to attack your space?\n- Which of your customers have vendor relationships with your competitors?\n\n---\n\n## The Stress Test Output\n\n```\nASSUMPTION: [Exact statement]\nSOURCE: [Where this came from — model, investor pitch, team gut feel]\n\nCOUNTER-EVIDENCE\n• [Specific evidence that challenges this assumption]\n• [Comparable failure case]\n• [Data point that contradicts the assumption]\n\nDOWNSIDE MODEL\n• Bear case (-30%): [Impact on plan]\n• Stress case (-50%): [Impact on plan]\n• Catastrophic (-80%): [Impact on plan — does the business survive?]\n\nSENSITIVITY\nThis assumption has [HIGH \u002F MEDIUM \u002F LOW] sensitivity.\nA 10% change → [X] change in outcome.\n\nHEDGE\n• Validation: [How to test this before betting on it]\n• Contingency: [Plan B if it's wrong]\n• Early warning: [Leading indicator to watch — and at what threshold to act]\n```\n","# \u002Fem:stress-test — Business Assumption Stress Testing\n\n**Command:** `\u002Fem:stress-test \u003Cassumption>`\n\nTake any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention.\n\n---\n\n## Why Most Assumptions Are Wrong\n\nFounders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started.\n\n**The most dangerous assumptions are the ones everyone agrees on.**\n\nWhen the whole team believes the $50M market is real, when every investor call goes well so you assume the round will close, when your model shows $2M ARR by December and nobody questions it — that's when you're most exposed.\n\nStress testing isn't pessimism. It's calibration.\n\n---\n\n## The Stress-Test Methodology\n\n### Step 1: Isolate the Assumption\n\nState it explicitly. Not \"our market is large\" but \"the total addressable market for B2B spend management software in German SMEs is €2.3B.\"\n\nThe more specific the assumption, the more testable it is. Vague assumptions are unfalsifiable — and therefore useless.\n\n**Common assumption types:**\n- **Market size** — TAM, SAM, SOM; growth rate; customer segments\n- **Customer behavior** — willingness to pay, churn, expansion, referrals\n- **Revenue model** — conversion rates, deal size, sales cycle, CAC\n- **Competitive position** — moat durability, competitor response speed, switching cost\n- **Execution** — team velocity, hire timeline, product timeline, operational scaling\n- **Macro** — regulatory environment, economic conditions, technology availability\n\n### Step 2: Find the Counter-Evidence\n\nFor every assumption, actively search for evidence that it's wrong.\n\nAsk:\n- Who has tried this and failed?\n- What data contradicts this assumption?\n- What does the bear case look like?\n- If a smart skeptic was looking at this, what would they point to?\n- What's the base rate for assumptions like this?\n\n**Sources of counter-evidence:**\n- Comparable companies that failed in adjacent markets\n- Customer churn data from similar businesses\n- Historical accuracy of similar forecasts\n- Industry reports with conflicting data\n- What competitors who tried this found\n\nThe goal isn't to find a reason to stop — it's to surface what you don't know.\n\n### Step 3: Model the Downside\n\nMost plans model the base case and the upside. Stress testing means modeling the downside explicitly.\n\n**For quantitative assumptions (revenue, growth, conversion):**\n\n| Scenario | Assumption Value | Probability | Impact |\n|----------|-----------------|-------------|--------|\n| Base case | [Original value] | ? | |\n| Bear case | -30% | ? | |\n| Stress case | -50% | ? | |\n| Catastrophic | -80% | ? | |\n\nKey question at each level: **Does the business survive? Does the plan make sense?**\n\n**For qualitative assumptions (moat, product-market fit, team capability):**\n\n- What's the earliest signal this assumption is wrong?\n- How long would it take you to notice?\n- What happens between when it breaks and when you detect it?\n\n### Step 4: Calculate Sensitivity\n\nSome assumptions matter more than others. Sensitivity analysis answers: **if this one assumption changes, how much does the outcome change?**\n\nExample: \n- If CAC doubles, how does that change runway?\n- If churn goes from 5% to 10%, how does that change NRR in 24 months?\n- If the deal cycle is 6 months instead of 3, how does that affect Q3 revenue?\n\nHigh sensitivity = the assumption is a key lever. Wrong = big problem.\n\n### Step 5: Propose the Hedge\n\nFor every high-risk assumption, there should be a hedge:\n\n- **Validation hedge** — test it before betting on it (pilot, customer conversation, small experiment)\n- **Contingency hedge** — if it's wrong, what's plan B?\n- **Early warning hedge** — what's the leading indicator that would tell you it's breaking before it's too late to act?\n\n---\n\n## Stress Test Patterns by Assumption Type\n\n### Revenue Projections\n\n**Common failures:**\n- Bottom-up model assumes 100% of pipeline converts\n- Doesn't account for deal slippage, churn, seasonality\n- New channel assumed to work before tested at scale\n\n**Stress questions:**\n- What's your actual historical win rate on pipeline?\n- If your top 3 deals slip to next quarter, what happens to the number?\n- What's the model look like if your new sales rep takes 4 months to ramp, not 2?\n- If expansion revenue doesn't materialize, what's the growth rate?\n\n**Test:** Build the revenue model from historical win rates, not hoped-for ones.\n\n### Market Size\n\n**Common failures:**\n- TAM calculated top-down from industry reports without bottoms-up validation\n- Conflating total market with serviceable market\n- Assuming 100% of SAM is reachable\n\n**Stress questions:**\n- How many companies in your ICP actually exist and can you name them?\n- What's your serviceable obtainable market in year 1-3?\n- What percentage of your ICP is currently spending on any solution to this problem?\n- What does \"winning\" look like and what market share does that require?\n\n**Test:** Build a list of target accounts. Count them. Multiply by ACV. That's your SAM.\n\n### Competitive Moat\n\n**Common failures:**\n- Moat is technology advantage that can be built in 6 months\n- Network effects that haven't yet materialized\n- Data advantage that requires scale you don't have\n\n**Stress questions:**\n- If a well-funded competitor copied your best feature in 90 days, what do customers do?\n- What's your retention rate among customers who have tried alternatives?\n- Is the moat real today or theoretical at scale?\n- What would it cost a competitor to reach feature parity?\n\n**Test:** Ask churned customers why they left and whether a competitor could have kept them.\n\n### Hiring Plan\n\n**Common failures:**\n- Time-to-hire assumes standard recruiting cycle, not current market\n- Ramp time not modeled (3-6 months before full productivity)\n- Key hire dependency: plan only works if specific person is hired\n\n**Stress questions:**\n- What happens if the VP Sales hire takes 5 months, not 2?\n- What does execution look like if you only hire 70% of planned headcount?\n- Which single person, if they left tomorrow, would most damage the plan?\n- Is the plan achievable with current team if hiring freezes?\n\n**Test:** Model the plan with 0 net new hires. What still works?\n\n### Competitive Response\n\n**Common failures:**\n- Assumes incumbents won't respond (they will if you're winning)\n- Underestimates speed of response\n- Doesn't model resource asymmetry\n\n**Stress questions:**\n- If the market leader copies your product in 6 months, how does pricing change?\n- What's your response if a competitor raises $30M to attack your space?\n- Which of your customers have vendor relationships with your competitors?\n\n---\n\n## The Stress Test Output\n\n```\nASSUMPTION: [Exact statement]\nSOURCE: [Where this came from — model, investor pitch, team gut feel]\n\nCOUNTER-EVIDENCE\n• [Specific evidence that challenges this assumption]\n• [Comparable failure case]\n• [Data point that contradicts the assumption]\n\nDOWNSIDE MODEL\n• Bear case (-30%): [Impact on plan]\n• Stress case (-50%): [Impact on plan]\n• Catastrophic (-80%): [Impact on plan — does the business survive?]\n\nSENSITIVITY\nThis assumption has [HIGH \u002F MEDIUM \u002F LOW] sensitivity.\nA 10% change → [X] change in outcome.\n\nHEDGE\n• Validation: [How to test this before betting on it]\n• Contingency: [Plan B if it's wrong]\n• Early warning: [Leading indicator to watch — and at what threshold to act]\n```\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","c-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fstress-test",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill stress-test",{"tool":47,"command":48},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill stress-test",{"tool":50,"command":51},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill stress-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fskills\u002Fstress-test\u002FSKILL.md",true,[],[56,83,109,138,158,181],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":29},"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",[],[63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","use","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":29},"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",[],[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,81,108],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":123,"publishedAt":29},"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",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[124,125,126,127,128,129,93,130,131,132,133,134,75,91,135,136,137,79,80,81],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":29},"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",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000037","律师与法务",[148,125,127,149,150,151,152,132,153,133,65,154,91,155,156,157,80],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":168,"publishedAt":29},"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",[164,167],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":145,"categoryName":146,"taxonomyType":121,"taxonomyTypeDesc":122},[93,169,125,127,170,171,130,72,172,133,173,174,75,175,176,177,81,178,179,180],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":29},"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",[],[130,188,189,96,190,191,192,193,65,75,194,78,80,81],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]