[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBFQ19RNANJPX3HZZ2JV46":3,"skill-same:01M6KBFQ19RNANJPX3HZZ2JV46":145},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6KBFQ19RNANJPX3HZZ2JV46","tech-debt-tracker",null,"Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.","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\u002Fengineering\u002Ftech-debt-tracker\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"tech","tech debt tracker","tech debt","tracker","track","code quality","legacy code","health assessment","sprints","technical debt","estimation","scoring","refactoring","remediation","severity","code","generate","cleanup","assessment","modernization","2026-11-10 10:12:30",false,"---\nname: tech-debt-tracker\ndescription: Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.\n---\n\n# Tech Debt Tracker\n\n**Tier**: POWERFUL ?  \n**Category**: Engineering Process Automation  \n**Expertise**: Code Quality, Technical Debt Management, Software Engineering\n\n## Overview\n\nTech debt is one of the most insidious challenges in software development - it compounds over time, slowing down development velocity, increasing maintenance costs, and reducing code quality. This skill provides a comprehensive framework for identifying, analyzing, prioritizing, and tracking technical debt across codebases.\n\nTech debt isn't just about messy code - it encompasses architectural shortcuts, missing tests, outdated dependencies, documentation gaps, and infrastructure compromises. Like financial debt, it accrues \"interest\" through increased development time, higher bug rates, and reduced team velocity.\n\n## What This Skill Provides\n\nThis skill offers three interconnected tools that form a complete tech debt management system:\n\n1. **Debt Scanner** - Automatically identifies tech debt signals in your codebase\n2. **Debt Prioritizer** - Analyzes and prioritizes debt items using cost-of-delay frameworks\n3. **Debt Dashboard** - Tracks debt trends over time and provides executive reporting\n\nTogether, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work.\n\n## Technical Debt Classification Framework\n→ See references\u002Fdebt-frameworks.md for details\n\n## Implementation Roadmap\n\n### Phase 1: Foundation (Weeks 1-2)\n1. Set up debt scanning infrastructure\n2. Establish debt taxonomy and scoring criteria\n3. Scan initial codebase and create baseline inventory\n4. Train team on debt identification and reporting\n\n### Phase 2: Process Integration (Weeks 3-4)\n1. Integrate debt tracking into sprint planning\n2. Establish debt budgets and allocation rules\n3. Create stakeholder reporting templates\n4. Set up automated debt scanning in CI\u002FCD\n\n### Phase 3: Optimization (Weeks 5-6)\n1. Refine scoring algorithms based on team feedback\n2. Implement trend analysis and predictive metrics\n3. Create specialized debt reduction initiatives\n4. Establish cross-team debt coordination processes\n\n### Phase 4: Maturity (Ongoing)\n1. Continuous improvement of detection algorithms\n2. Advanced analytics and prediction models\n3. Integration with planning and project management tools\n4. Organization-wide debt management best practices\n\n## Success Criteria\n\n**Quantitative Metrics:**\n- 25% reduction in debt interest rate within 6 months\n- 15% improvement in development velocity\n- 30% reduction in production defects\n- 20% faster code review cycles\n\n**Qualitative Metrics:**\n- Improved developer satisfaction scores\n- Reduced context switching during feature development\n- Faster onboarding for new team members\n- Better predictability in feature delivery timelines\n\n## Common Pitfalls and How to Avoid Them\n\n### 1. Analysis Paralysis\n**Problem**: Spending too much time analyzing debt instead of fixing it.\n**Solution**: Set time limits for analysis, use \"good enough\" scoring for most items.\n\n### 2. Perfectionism\n**Problem**: Trying to eliminate all debt instead of managing it.\n**Solution**: Focus on high-impact debt, accept that some debt is acceptable.\n\n### 3. Ignoring Business Context\n**Problem**: Prioritizing technical elegance over business value.\n**Solution**: Always tie debt work to business outcomes and customer impact.\n\n### 4. Inconsistent Application\n**Problem**: Some teams adopt practices while others ignore them.\n**Solution**: Make debt tracking part of standard development workflow.\n\n### 5. Tool Over-Engineering\n**Problem**: Building complex debt management systems that nobody uses.\n**Solution**: Start simple, iterate based on actual usage patterns.\n\nTechnical debt management is not just about writing better code - it's about creating sustainable development practices that balance short-term delivery pressure with long-term system health. Use these tools and frameworks to make informed decisions about when and how to invest in debt reduction.\n","# Tech Debt Tracker\n\n**Tier**: POWERFUL ?  \n**Category**: Engineering Process Automation  \n**Expertise**: Code Quality, Technical Debt Management, Software Engineering\n\n## Overview\n\nTech debt is one of the most insidious challenges in software development - it compounds over time, slowing down development velocity, increasing maintenance costs, and reducing code quality. This skill provides a comprehensive framework for identifying, analyzing, prioritizing, and tracking technical debt across codebases.\n\nTech debt isn't just about messy code - it encompasses architectural shortcuts, missing tests, outdated dependencies, documentation gaps, and infrastructure compromises. Like financial debt, it accrues \"interest\" through increased development time, higher bug rates, and reduced team velocity.\n\n## What This Skill Provides\n\nThis skill offers three interconnected tools that form a complete tech debt management system:\n\n1. **Debt Scanner** - Automatically identifies tech debt signals in your codebase\n2. **Debt Prioritizer** - Analyzes and prioritizes debt items using cost-of-delay frameworks\n3. **Debt Dashboard** - Tracks debt trends over time and provides executive reporting\n\nTogether, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work.\n\n## Technical Debt Classification Framework\n→ See references\u002Fdebt-frameworks.md for details\n\n## Implementation Roadmap\n\n### Phase 1: Foundation (Weeks 1-2)\n1. Set up debt scanning infrastructure\n2. Establish debt taxonomy and scoring criteria\n3. Scan initial codebase and create baseline inventory\n4. Train team on debt identification and reporting\n\n### Phase 2: Process Integration (Weeks 3-4)\n1. Integrate debt tracking into sprint planning\n2. Establish debt budgets and allocation rules\n3. Create stakeholder reporting templates\n4. Set up automated debt scanning in CI\u002FCD\n\n### Phase 3: Optimization (Weeks 5-6)\n1. Refine scoring algorithms based on team feedback\n2. Implement trend analysis and predictive metrics\n3. Create specialized debt reduction initiatives\n4. Establish cross-team debt coordination processes\n\n### Phase 4: Maturity (Ongoing)\n1. Continuous improvement of detection algorithms\n2. Advanced analytics and prediction models\n3. Integration with planning and project management tools\n4. Organization-wide debt management best practices\n\n## Success Criteria\n\n**Quantitative Metrics:**\n- 25% reduction in debt interest rate within 6 months\n- 15% improvement in development velocity\n- 30% reduction in production defects\n- 20% faster code review cycles\n\n**Qualitative Metrics:**\n- Improved developer satisfaction scores\n- Reduced context switching during feature development\n- Faster onboarding for new team members\n- Better predictability in feature delivery timelines\n\n## Common Pitfalls and How to Avoid Them\n\n### 1. Analysis Paralysis\n**Problem**: Spending too much time analyzing debt instead of fixing it.\n**Solution**: Set time limits for analysis, use \"good enough\" scoring for most items.\n\n### 2. Perfectionism\n**Problem**: Trying to eliminate all debt instead of managing it.\n**Solution**: Focus on high-impact debt, accept that some debt is acceptable.\n\n### 3. Ignoring Business Context\n**Problem**: Prioritizing technical elegance over business value.\n**Solution**: Always tie debt work to business outcomes and customer impact.\n\n### 4. Inconsistent Application\n**Problem**: Some teams adopt practices while others ignore them.\n**Solution**: Make debt tracking part of standard development workflow.\n\n### 5. Tool Over-Engineering\n**Problem**: Building complex debt management systems that nobody uses.\n**Solution**: Start simple, iterate based on actual usage patterns.\n\nTechnical debt management is not just about writing better code - it's about creating sustainable development practices that balance short-term delivery pressure with long-term system health. Use these tools and frameworks to make informed decisions about when and how to invest in debt reduction.\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Ftech-debt-tracker",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill tech-debt-tracker",{"tool":63,"command":64},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill tech-debt-tracker",{"tool":66,"command":67},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill tech-debt-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002FSKILL.md",true,[71,77,81,87,91,95,99,105,109,113,117,121,125,129,133,137,141],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Fhistorical_debt_2024-01-15.json","ASSET","资产文件",8190,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fhistorical_debt_2024-01-15.json",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Fhistorical_debt_2024-02-01.json",6542,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fhistorical_debt_2024-02-01.json",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Fsample_codebase\u002Fsrc\u002Ffrontend.js","SCRIPT","脚本",14891,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fsample_codebase\u002Fsrc\u002Ffrontend.js",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fsample_codebase\u002Fsrc\u002Fpayment_processor.py",13774,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fsample_codebase\u002Fsrc\u002Fpayment_processor.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Fsample_codebase\u002Fsrc\u002Fuser_service.py",9498,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fsample_codebase\u002Fsrc\u002Fuser_service.py",{"path":96,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fsample_debt_inventory.json",7788,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fassets\u002Fsample_debt_inventory.json",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"expected_outputs\u002Fsample_dashboard_output.json","REFERENCE","参考文档",5274,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fexpected_outputs\u002Fsample_dashboard_output.json",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"expected_outputs\u002Fsample_prioritization_output.json",45654,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fexpected_outputs\u002Fsample_prioritization_output.json",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"expected_outputs\u002Fsample_scan_output.json",58350,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fexpected_outputs\u002Fsample_scan_output.json",{"path":114,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":115,"sourceHtmlUrl":116},"README.md",9509,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002FREADME.md",{"path":118,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fdebt-classification-taxonomy.md",10424,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Freferences\u002Fdebt-classification-taxonomy.md",{"path":122,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fdebt-frameworks.md",14015,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Freferences\u002Fdebt-frameworks.md",{"path":126,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fprioritization-framework.md",10889,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Freferences\u002Fprioritization-framework.md",{"path":130,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fstakeholder-communication-templates.md",12904,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Freferences\u002Fstakeholder-communication-templates.md",{"path":134,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":135,"sourceHtmlUrl":136},"scripts\u002Fdebt_dashboard.py",40885,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fscripts\u002Fdebt_dashboard.py",{"path":138,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":139,"sourceHtmlUrl":140},"scripts\u002Fdebt_prioritizer.py",34696,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fscripts\u002Fdebt_prioritizer.py",{"path":142,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":143,"sourceHtmlUrl":144},"scripts\u002Fdebt_scanner.py",26302,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Ftech-debt-tracker\u002Fscripts\u002Fdebt_scanner.py",[146,176,201,226,258,278],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":44},"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",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":44},"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",[],[183,184,185,186,187,188,189,190,163,164,191,192,193,194,195,196,197,198,199,200],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":44},"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",[],[208,209,210,211,212,213,214,215,216,164,217,218,219,220,221,222,223,224,225,175],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":240,"publishedAt":44},"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",[232,237],{"categoryNo":233,"categoryName":234,"taxonomyType":235,"taxonomyTypeDesc":236},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":238,"categoryName":239,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[241,242,225,243,244,245,246,247,248,164,249,250,251,252,253,254,255,256,175,257],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":259,"name":260,"nameZh":6,"description":261,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":262,"categories":263,"keywords":265,"publishedAt":44},"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",[264],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},[266,242,225,267,268,269,270,271,156,272,248,273,209,274,275,276,192,253,175,277],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":279,"name":280,"nameZh":6,"description":281,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":282,"categories":283,"keywords":291,"publishedAt":44},"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",[284,287,290],{"categoryNo":285,"categoryName":286,"taxonomyType":235,"taxonomyTypeDesc":236},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":288,"categoryName":289,"taxonomyType":235,"taxonomyTypeDesc":236},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},[292,293,242,225,267,294,295,160,248,296,297,298,299,300,193,301,302,303,304,175],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]