[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KAS4DJ8V50J4ZVK49XPKHM":3,"skill-same:01M6KAS4DJ8V50J4ZVK49XPKHM":92},{"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":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6KAS4DJ8V50J4ZVK49XPKHM","board-meeting",null,"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.","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\u002Fc-level-advisor\u002Fboard-meeting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"meeting","board meeting","board","context","suite","for","layer","calls","strategic","loading","deliberation","use","review","question","decisions","decision","multi-agent","critic","analysis","memory","2026-11-10 10:12:30",false,"---\nname: \"board-meeting\"\ndescription: \"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Md Faiz Alam\n  category: c-level\n  domain: board-protocol\n  updated: 2026-03-05\n  frameworks: 6-phase-board, two-layer-memory, independent-contributions\n---\n\n# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:board, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:board [topic]` — e.g. `\u002Fcs:board Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `memory\u002Fcompany-context.md`\n2. Load `memory\u002Fboard-meetings\u002Fdecisions.md` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 9 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `agent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:board resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- **Layer 2:** Append approved decisions → `memory\u002Fboard-meetings\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md          # Layer 2 — founder-approved only (Phase 1 loads this)\n├── YYYY-MM-DD-raw.md     # Layer 1 — full transcripts (never auto-loaded)\n└── archive\u002FYYYY\u002F         # Raw transcripts after 90 days\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads decisions.md only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n","# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:board, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:board [topic]` — e.g. `\u002Fcs:board Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `memory\u002Fcompany-context.md`\n2. Load `memory\u002Fboard-meetings\u002Fdecisions.md` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 9 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n• [Finding] — [VERIFIED\u002FASSUMED] — ?\u002F?\u002F?\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `agent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:board resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- **Layer 2:** Append approved decisions → `memory\u002Fboard-meetings\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md          # Layer 2 — founder-approved only (Phase 1 loads this)\n├── YYYY-MM-DD-raw.md     # Layer 1 — full transcripts (never auto-loaded)\n└── archive\u002FYYYY\u002F         # Raw transcripts after 90 days\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads decisions.md only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":54,"frameworks":55},"Md Faiz Alam","board-protocol",1772668800000,"1.0.0","c-level","6-phase-board, two-layer-memory, independent-contributions","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","c-level-advisor\u002Fboard-meeting",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill board-meeting",{"tool":70,"command":71},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill board-meeting",{"tool":73,"command":74},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill board-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fboard-meeting\u002FSKILL.md",true,[78,84,88],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fmeeting-facilitation.md","REFERENCE","参考文档",8212,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fboard-meeting\u002Freferences\u002Fmeeting-facilitation.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"templates\u002Fmeeting-agenda.md",1976,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-agenda.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"templates\u002Fmeeting-minutes.md",2465,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-minutes.md",[93,120,145,170,202,221],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":102,"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",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[103,104,105,106,107,108,109,42,35,110,111,112,113,114,115,116,117,118,119,29],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[127,128,129,130,131,132,133,134,42,35,135,136,137,138,139,140,141,142,143,144],"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":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[152,153,154,155,156,157,158,159,160,35,161,162,163,164,165,166,167,168,169,29],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":184,"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",[176,181],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[185,186,169,187,188,189,190,191,192,35,193,194,195,196,197,198,199,200,29,201],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"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",[208],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},[210,186,169,36,211,212,213,214,103,215,192,216,153,217,218,219,136,197,29,220],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":234,"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",[227,230,233],{"categoryNo":228,"categoryName":229,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":231,"categoryName":232,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},[235,236,186,169,36,237,238,107,192,239,240,241,242,243,137,244,245,246,247,29],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]