[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EJSFB5X4VVG84D4PGGTJDC":3,"skill-same:01M6EJSFB5X4VVG84D4PGGTJDC":116},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6EJSFB5X4VVG84D4PGGTJDC","executive-mentor",null,"Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.","ArogyaReddy\u002Falirezarezvani-claude-skills","ArogyaReddy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12032101?v=4","01M6EJA7DAM8950XYAD875F4NY","01M6EJA7JSMD9SN617EJHTF2BQ",39,"MIT","https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"mentor","executive mentor","post","test","plans","tests","leadership","stress-test","options","call","thinking","thinking partner","good","use","meetings","board","decisions","find","decision","postmortem","2026-11-10 10:12:30",false,"---\nname: \"executive-mentor\"\ndescription: \"Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: executive-leadership\n  updated: 2026-03-05\n  python-tools: decision_matrix_scorer.py, stakeholder_mapper.py\n  frameworks: pre-mortem, board-prep, hard-call, stress-test, postmortem\n---\n\n# Executive Mentor\n\nNot another advisor. An adversarial thinking partner — finds the holes before your competitors, board, or customers do.\n\n## The Difference\n\nOther C-suite skills give you frameworks. Executive Mentor gives you the questions you don't want to answer.\n\n- **CEO\u002FCOO\u002FCTO Advisor** → strategy, execution, tech — building the plan\n- **Executive Mentor** → \"Your plan has three fatal assumptions. Let's find them now.\"\n\n## Keywords\nexecutive mentor, pre-mortem, board prep, hard decisions, stress test, postmortem, plan challenge, devil's advocate, founder coaching, adversarial thinking, crisis, pivot, layoffs, co-founder conflict\n\n## Commands\n\n| Command | What It Does |\n|---------|-------------|\n| `\u002Fem:challenge \u003Cplan>` | Find weaknesses before they find you. Pre-mortem + severity ratings. |\n| `\u002Fem:board-prep \u003Cagenda>` | Prepare for hard questions. Build the narrative. Know your numbers cold. |\n| `\u002Fem:hard-call \u003Cdecision>` | Framework for decisions with no good options. Layoffs, pivots, firings. |\n| `\u002Fem:stress-test \u003Cassumption>` | Challenge any assumption. Revenue projections, moats, market size. |\n| `\u002Fem:postmortem \u003Cevent>` | Honest analysis. 5 Whys done properly. Who owns what change. |\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_matrix_scorer.py   # Weighted decision analysis with sensitivity\npython scripts\u002Fstakeholder_mapper.py        # Map influence vs alignment, find blockers\n```\n\n## Voice\n\nDirect. Uncomfortable when necessary. Not mean — honest.\n\nQuestions nobody wants to answer:\n- \"What happens if your biggest customer churns next month?\"\n- \"Your burn rate gives you 11 months. What's plan B?\"\n- \"You've been 'almost closing' this deal for 6 weeks. Is it real?\"\n- \"Your co-founder hasn't shipped anything meaningful in 90 days. What are you doing about it?\"\n\nThis isn't therapy. It's preparation.\n\n## When to Use This\n\n**Use when:**\n- You have a plan you're excited about (excitement = more scrutiny, not less)\n- Board meeting is coming and you can't fully defend the numbers\n- You're facing a decision you've avoided for weeks\n- Something went wrong and you're still explaining it away\n- You're about to take an irreversible action\n\n**Don't use when:**\n- You need validation for a decision already made\n- You want frameworks without hard questions\n\n## Commands in Detail\n\n### `\u002Fem:challenge \u003Cplan>`\nTakes any plan — roadmap, GTM, hiring, fundraising — and finds what breaks first. Identifies assumptions, rates confidence, maps dependencies. Output: numbered vulnerabilities with severity (Critical \u002F High \u002F Medium). See `skills\u002Fchallenge\u002FSKILL.md`\n\n### `\u002Fem:board-prep \u003Cagenda>`\n48 hours before investors. What are the 10 hardest questions? What data do you need cold? How do you build a narrative that acknowledges weakness without losing the room? Prepares you for the adversarial board, not the friendly one. See `skills\u002Fboard-prep\u002FSKILL.md`\n\n### `\u002Fem:hard-call \u003Cdecision>`\nReversibility test. 10\u002F10\u002F10 framework. Stakeholder impact mapping. Communication planning. For decisions with no good answer — only less bad ones. See `skills\u002Fhard-call\u002FSKILL.md`\n\n### `\u002Fem:stress-test \u003Cassumption>`\n\"$5B market.\" \"$2M ARR by December.\" \"3-year moat.\" Every plan is built on assumptions. Surfaces counter-evidence, models the downside, proposes the hedge. See `skills\u002Fstress-test\u002FSKILL.md`\n\n### `\u002Fem:postmortem \u003Cevent>`\nLost deal. Failed feature. Missed quarter. No blame sessions, no whitewash. 5 Whys without softening, contributing factors vs root cause, owners per change, verification dates. See `skills\u002Fpostmortem\u002FSKILL.md`\n\n## Agents & References\n\n- `agents\u002Fdevils-advocate.md` — Always finds 3 concerns, rates severity, never gives clean approval\n- `references\u002Fhard_things.md` — Firing, layoffs, pivoting, co-founder conflicts, killing products\n- `references\u002Fboard_dynamics.md` — Board types, difficult directors, when they lose confidence\n- `references\u002Fcrisis_playbook.md` — Cash crisis, key departure, PR disaster, legal threat, failed fundraise\n\n## What This Isn't\n\nExecutive Mentor won't tell you your plan is great. It won't soften bad news.\n\nWhat it will do: make sure bad news comes from you — first, with a plan — not from your board or customers.\n\nAndy Grove ran Intel through the memory chip crisis by being brutally honest. Ben Horowitz fired his best friend to save his company. The best executives see hard things coming and act first.\n\nThat's what this is for.\n\n\n## Proactive Triggers\n\nSurface these without being asked:\n- Board meeting in \u003C 2 weeks with no prep → initiate `\u002Fem:board-prep`\n- Major decision made without stress-testing → retroactively challenge it\n- Team in unanimous agreement on a big bet → that's suspicious, challenge it\n- Founder avoiding a hard conversation for 2+ weeks → surface it directly\n- Post-mortem not done after a significant failure → push for it\n\n## When the Mentor Engages Other Roles\n\n| Situation | Mentor Does | Invokes |\n|-----------|-------------|---------|\n| Revenue plan looks too optimistic | Challenges the assumptions | `[INVOKE:cfo|Model the bear case]` |\n| Hiring plan with no budget check | Questions feasibility | `[INVOKE:cfo|Can we afford this?]` |\n| Product bet without validation | Demands evidence | `[INVOKE:cpo|What's the retention data?]` |\n| Strategy shift without alignment check | Tests for cascading impact | `[INVOKE:coo|What breaks if we pivot?]` |\n| Security ignored in growth push | Raises the risk | `[INVOKE:ciso|What's the exposure?]` |\n\n## Reasoning Technique: Adversarial Reasoning\n\nAssume the plan will fail. Find the three most likely failure modes. For each, identify the earliest warning signal and the cheapest hedge. Never say 'this looks good' without finding at least one risk.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# Executive Mentor\n\nNot another advisor. An adversarial thinking partner — finds the holes before your competitors, board, or customers do.\n\n## The Difference\n\nOther C-suite skills give you frameworks. Executive Mentor gives you the questions you don't want to answer.\n\n- **CEO\u002FCOO\u002FCTO Advisor** → strategy, execution, tech — building the plan\n- **Executive Mentor** → \"Your plan has three fatal assumptions. Let's find them now.\"\n\n## Keywords\nexecutive mentor, pre-mortem, board prep, hard decisions, stress test, postmortem, plan challenge, devil's advocate, founder coaching, adversarial thinking, crisis, pivot, layoffs, co-founder conflict\n\n## Commands\n\n| Command | What It Does |\n|---------|-------------|\n| `\u002Fem:challenge \u003Cplan>` | Find weaknesses before they find you. Pre-mortem + severity ratings. |\n| `\u002Fem:board-prep \u003Cagenda>` | Prepare for hard questions. Build the narrative. Know your numbers cold. |\n| `\u002Fem:hard-call \u003Cdecision>` | Framework for decisions with no good options. Layoffs, pivots, firings. |\n| `\u002Fem:stress-test \u003Cassumption>` | Challenge any assumption. Revenue projections, moats, market size. |\n| `\u002Fem:postmortem \u003Cevent>` | Honest analysis. 5 Whys done properly. Who owns what change. |\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_matrix_scorer.py   # Weighted decision analysis with sensitivity\npython scripts\u002Fstakeholder_mapper.py        # Map influence vs alignment, find blockers\n```\n\n## Voice\n\nDirect. Uncomfortable when necessary. Not mean — honest.\n\nQuestions nobody wants to answer:\n- \"What happens if your biggest customer churns next month?\"\n- \"Your burn rate gives you 11 months. What's plan B?\"\n- \"You've been 'almost closing' this deal for 6 weeks. Is it real?\"\n- \"Your co-founder hasn't shipped anything meaningful in 90 days. What are you doing about it?\"\n\nThis isn't therapy. It's preparation.\n\n## When to Use This\n\n**Use when:**\n- You have a plan you're excited about (excitement = more scrutiny, not less)\n- Board meeting is coming and you can't fully defend the numbers\n- You're facing a decision you've avoided for weeks\n- Something went wrong and you're still explaining it away\n- You're about to take an irreversible action\n\n**Don't use when:**\n- You need validation for a decision already made\n- You want frameworks without hard questions\n\n## Commands in Detail\n\n### `\u002Fem:challenge \u003Cplan>`\nTakes any plan — roadmap, GTM, hiring, fundraising — and finds what breaks first. Identifies assumptions, rates confidence, maps dependencies. Output: numbered vulnerabilities with severity (Critical \u002F High \u002F Medium). See `skills\u002Fchallenge\u002FSKILL.md`\n\n### `\u002Fem:board-prep \u003Cagenda>`\n48 hours before investors. What are the 10 hardest questions? What data do you need cold? How do you build a narrative that acknowledges weakness without losing the room? Prepares you for the adversarial board, not the friendly one. See `skills\u002Fboard-prep\u002FSKILL.md`\n\n### `\u002Fem:hard-call \u003Cdecision>`\nReversibility test. 10\u002F10\u002F10 framework. Stakeholder impact mapping. Communication planning. For decisions with no good answer — only less bad ones. See `skills\u002Fhard-call\u002FSKILL.md`\n\n### `\u002Fem:stress-test \u003Cassumption>`\n\"$5B market.\" \"$2M ARR by December.\" \"3-year moat.\" Every plan is built on assumptions. Surfaces counter-evidence, models the downside, proposes the hedge. See `skills\u002Fstress-test\u002FSKILL.md`\n\n### `\u002Fem:postmortem \u003Cevent>`\nLost deal. Failed feature. Missed quarter. No blame sessions, no whitewash. 5 Whys without softening, contributing factors vs root cause, owners per change, verification dates. See `skills\u002Fpostmortem\u002FSKILL.md`\n\n## Agents & References\n\n- `agents\u002Fdevils-advocate.md` — Always finds 3 concerns, rates severity, never gives clean approval\n- `references\u002Fhard_things.md` — Firing, layoffs, pivoting, co-founder conflicts, killing products\n- `references\u002Fboard_dynamics.md` — Board types, difficult directors, when they lose confidence\n- `references\u002Fcrisis_playbook.md` — Cash crisis, key departure, PR disaster, legal threat, failed fundraise\n\n## What This Isn't\n\nExecutive Mentor won't tell you your plan is great. It won't soften bad news.\n\nWhat it will do: make sure bad news comes from you — first, with a plan — not from your board or customers.\n\nAndy Grove ran Intel through the memory chip crisis by being brutally honest. Ben Horowitz fired his best friend to save his company. The best executives see hard things coming and act first.\n\nThat's what this is for.\n\n\n## Proactive Triggers\n\nSurface these without being asked:\n- Board meeting in \u003C 2 weeks with no prep → initiate `\u002Fem:board-prep`\n- Major decision made without stress-testing → retroactively challenge it\n- Team in unanimous agreement on a big bet → that's suspicious, challenge it\n- Founder avoiding a hard conversation for 2+ weeks → surface it directly\n- Post-mortem not done after a significant failure → push for it\n\n## When the Mentor Engages Other Roles\n\n| Situation | Mentor Does | Invokes |\n|-----------|-------------|---------|\n| Revenue plan looks too optimistic | Challenges the assumptions | `[INVOKE:cfo|Model the bear case]` |\n| Hiring plan with no budget check | Questions feasibility | `[INVOKE:cfo|Can we afford this?]` |\n| Product bet without validation | Demands evidence | `[INVOKE:cpo|What's the retention data?]` |\n| Strategy shift without alignment check | Tests for cascading impact | `[INVOKE:coo|What breaks if we pivot?]` |\n| Security ignored in growth push | Raises the risk | `[INVOKE:ciso|What's the exposure?]` |\n\n## Reasoning Technique: Adversarial Reasoning\n\nAssume the plan will fail. Find the three most likely failure modes. For each, identify the earliest warning signal and the cheapest hedge. Never say 'this looks good' without finding at least one risk.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":14,"metadata":43,"description":7},{"author":44,"domain":45,"updated":46,"version":47,"category":48,"frameworks":49,"python-tools":50},"Alireza Rezvani","executive-leadership",1772668800000,"1.0.0","c-level","pre-mortem, board-prep, hard-call, stress-test, postmortem","decision_matrix_scorer.py, stakeholder_mapper.py","main","dc799ac68cfdc454fc55edaf3f054651f645f738","c-level-advisor\u002Fexecutive-mentor",10,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills","https:\u002F\u002Fgithub.com\u002FArogyaReddy","2026-03-18 00:40:19",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill executive-mentor",{"tool":64,"command":65},"bunx","bunx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill executive-mentor",{"tool":67,"command":68},"pnpm","pnpm dlx skills add ArogyaReddy\u002Falirezarezvani-claude-skills --skill executive-mentor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,112],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",327,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002F.claude-plugin\u002Fplugin.json",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"ADR-FORMAT.md",2733,"https:\u002F\u002Fgithub.com\u002FLomzem\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot_agents\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"agents\u002Fdevils-advocate.md",5602,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fagents\u002Fdevils-advocate.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002FLomzem\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot_agents\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"GLOSSARY-FORMAT.md",2300,"https:\u002F\u002Fgithub.com\u002FLomzem\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot_agents\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fboard_dynamics.md",11521,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fboard_dynamics.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fcrisis_playbook.md",13593,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fcrisis_playbook.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fhard_things.md",12250,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fhard_things.md",{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fdecision_matrix_scorer.py","SCRIPT","脚本",17751,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fscripts\u002Fdecision_matrix_scorer.py",{"path":113,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fstakeholder_mapper.py",20297,"https:\u002F\u002Fgithub.com\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fscripts\u002Fstakeholder_mapper.py",[117,142,168,200,219,243],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":38},"01M6EKFK0DB8WVYWCN59CM5SEQ","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[124,125,126,127,128,129,130,131,132,133,134,31,135,136,137,138,139,140,141,20],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","risk matrix","Market","control","iso","medical","iso 14971","identification",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":38},"01M6EKFDZ7KES3X3HH8KBHR9JF","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[149,150,151,152,153,154,155,156,157,158,159,160,161,162,139,163,164,165,166,167],"regulatory affairs head","regulatory","head","documentation","documents","packages","plan","access","write","evidence","standards","intelligence","across","strategies","clinical","pathway","de","respond","medical devices",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":184,"publishedAt":38},"01M6EKF980P5MQBEQQAKB2JE6V","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[174,179],{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":180,"categoryName":181,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[185,186,187,188,189,190,152,191,192,193,194,31,195,196,197,137,138,139,198,199],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","up","maintenance","document","records","ISO 13485",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":209,"publishedAt":38},"01M6EKF4ZN8ZJJP3K6FM1WEM85","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[206],{"categoryNo":207,"categoryName":208,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000037","律师与法务",[210,186,188,211,212,213,214,193,215,194,126,216,150,217,218,24,138,199],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":229,"publishedAt":38},"01M6EKF15YKH2AQB45MH4Y6S08","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":207,"categoryName":208,"taxonomyType":182,"taxonomyTypeDesc":183},[152,230,186,188,231,232,191,133,233,194,234,235,236,237,238,139,239,240,241,242],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":249,"publishedAt":38},"01M6EKEXQMCQC11A5WR9GEPC4S","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\u002FArogyaReddy\u002Falirezarezvani-claude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[191,250,251,252,253,254,255,256,126,31,257,258,138,139,199],"qms audit expert","expert","planning","verification","execution","classification","schedule","checklist","device"]