[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KAVXZCF9XD1N7GPN3CMK85":3,"skill-same:01M6KAVXZCF9XD1N7GPN3CMK85":89},{"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},"01M6KAVXZCF9XD1N7GPN3CMK85","decision-logger",null,"Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with \u002Fcs:decisions, or checking overdue action items with \u002Fcs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.","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\u002Fdecision-logger\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"decision","decision logger","logger","tracker","for","layer","action","past","meeting","with","scripts","founder","review","use","board","board meeting","decisions","logging","architecture","memory","2026-11-10 10:12:30",false,"---\nname: \"decision-logger\"\ndescription: \"Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with \u002Fcs:decisions, or checking overdue action items with \u002Fcs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Md Faiz Alam\n  category: c-level\n  domain: decision-memory\n  updated: 2026-03-05\n  python-tools: scripts\u002Fdecision_tracker.py\n---\n\n# Decision Logger\n\nTwo-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.\n\n## Keywords\ndecision log, memory, approved decisions, action items, board minutes, \u002Fcs:decisions, \u002Fcs:review, conflict detection, DO_NOT_RESURFACE\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_tracker.py --demo             # See sample output\npython scripts\u002Fdecision_tracker.py --summary          # Overview + overdue\npython scripts\u002Fdecision_tracker.py --overdue          # Past-deadline actions\npython scripts\u002Fdecision_tracker.py --conflicts        # Contradiction detection\npython scripts\u002Fdecision_tracker.py --owner \"CTO\"      # Filter by owner\npython scripts\u002Fdecision_tracker.py --search \"pricing\" # Search decisions\n```\n\n---\n\n## Commands\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fcs:decisions` | Last 10 approved decisions |\n| `\u002Fcs:decisions --all` | Full history |\n| `\u002Fcs:decisions --owner CMO` | Filter by owner |\n| `\u002Fcs:decisions --topic pricing` | Search by keyword |\n| `\u002Fcs:review` | Action items due within 7 days |\n| `\u002Fcs:review --overdue` | Items past deadline |\n\n---\n\n## Two-Layer Architecture\n\n### Layer 1 — Raw Transcripts\n**Location:** `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis\n- All debates, including rejected arguments\n- **NEVER auto-loaded.** Only on explicit founder request.\n- Archive after 90 days → `memory\u002Fboard-meetings\u002Farchive\u002FYYYY\u002F`\n\n### Layer 2 — Approved Decisions\n**Location:** `memory\u002Fboard-meetings\u002Fdecisions.md`\n- ONLY founder-approved decisions, action items, user corrections\n- **Loaded automatically in Phase 1 of every board meeting**\n- Append-only. Decisions are never deleted — only superseded.\n- Managed by Chief of Staff after Phase 5. Never written by agents directly.\n\n---\n\n## Decision Entry Format\n\n```markdown\n## [YYYY-MM-DD] — [AGENDA ITEM TITLE]\n\n**Decision:** [One clear statement of what was decided.]\n**Owner:** [One person or role — accountable for execution.]\n**Deadline:** [YYYY-MM-DD]\n**Review:** [YYYY-MM-DD]\n**Rationale:** [Why this over alternatives. 1-2 sentences.]\n\n**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]\n\n**Rejected:**\n- [Proposal] — [reason] [DO_NOT_RESURFACE]\n\n**Action Items:**\n- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]\n\n**Supersedes:** [DATE of previous decision on same topic, if any]\n**Superseded by:** [Filled in retroactively if overridden later]\n**Raw transcript:** memory\u002Fboard-meetings\u002F[DATE]-raw.md\n```\n\n---\n\n## Conflict Detection\n\nBefore logging, Chief of Staff checks for:\n1. **DO_NOT_RESURFACE violations** — new decision matches a rejected proposal\n2. **Topic contradictions** — two active decisions on same topic with different conclusions\n3. **Owner conflicts** — same action assigned to different people in different decisions\n\nWhen a conflict is found:\n```\n⚠️ DECISION CONFLICT\nNew: [text]\nConflicts with: [DATE] — [existing text]\n\nOptions: (1) Supersede old  (2) Merge  (3) Defer to founder\n```\n\n**DO_NOT_RESURFACE enforcement:**\n```\n? BLOCKED: \"[Proposal]\" was rejected on [DATE]. Reason: [reason].\nTo reopen: founder must explicitly say \"reopen [topic] from [DATE]\".\n```\n\n---\n\n## Logging Workflow (Post Phase 5)\n\n1. Founder approves synthesis\n2. Write Layer 1 raw transcript → `YYYY-MM-DD-raw.md`\n3. Check conflicts against `decisions.md`\n4. Surface conflicts → wait for founder resolution\n5. Append approved entries to `decisions.md`\n6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added\n\n---\n\n## Marking Actions Complete\n\n```markdown\n- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]\n```\n\nNever delete completed items. The history is the record.\n\n---\n\n## File Structure\n\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md       # Layer 2: append-only, founder-approved\n├── YYYY-MM-DD-raw.md  # Layer 1: full transcript per meeting\n└── archive\u002FYYYY\u002F      # Raw files after 90 days\n```\n\n---\n\n## References\n- `templates\u002Fdecision-entry.md` — single entry template with field rules\n- `scripts\u002Fdecision_tracker.py` — CLI parser, overdue tracker, conflict detector\n","# Decision Logger\n\nTwo-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.\n\n## Keywords\ndecision log, memory, approved decisions, action items, board minutes, \u002Fcs:decisions, \u002Fcs:review, conflict detection, DO_NOT_RESURFACE\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_tracker.py --demo             # See sample output\npython scripts\u002Fdecision_tracker.py --summary          # Overview + overdue\npython scripts\u002Fdecision_tracker.py --overdue          # Past-deadline actions\npython scripts\u002Fdecision_tracker.py --conflicts        # Contradiction detection\npython scripts\u002Fdecision_tracker.py --owner \"CTO\"      # Filter by owner\npython scripts\u002Fdecision_tracker.py --search \"pricing\" # Search decisions\n```\n\n---\n\n## Commands\n\n| Command | Effect |\n|---------|--------|\n| `\u002Fcs:decisions` | Last 10 approved decisions |\n| `\u002Fcs:decisions --all` | Full history |\n| `\u002Fcs:decisions --owner CMO` | Filter by owner |\n| `\u002Fcs:decisions --topic pricing` | Search by keyword |\n| `\u002Fcs:review` | Action items due within 7 days |\n| `\u002Fcs:review --overdue` | Items past deadline |\n\n---\n\n## Two-Layer Architecture\n\n### Layer 1 — Raw Transcripts\n**Location:** `memory\u002Fboard-meetings\u002FYYYY-MM-DD-raw.md`\n- Full Phase 2 agent contributions, Phase 3 critique, Phase 4 synthesis\n- All debates, including rejected arguments\n- **NEVER auto-loaded.** Only on explicit founder request.\n- Archive after 90 days → `memory\u002Fboard-meetings\u002Farchive\u002FYYYY\u002F`\n\n### Layer 2 — Approved Decisions\n**Location:** `memory\u002Fboard-meetings\u002Fdecisions.md`\n- ONLY founder-approved decisions, action items, user corrections\n- **Loaded automatically in Phase 1 of every board meeting**\n- Append-only. Decisions are never deleted — only superseded.\n- Managed by Chief of Staff after Phase 5. Never written by agents directly.\n\n---\n\n## Decision Entry Format\n\n```markdown\n## [YYYY-MM-DD] — [AGENDA ITEM TITLE]\n\n**Decision:** [One clear statement of what was decided.]\n**Owner:** [One person or role — accountable for execution.]\n**Deadline:** [YYYY-MM-DD]\n**Review:** [YYYY-MM-DD]\n**Rationale:** [Why this over alternatives. 1-2 sentences.]\n\n**User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.]\n\n**Rejected:**\n- [Proposal] — [reason] [DO_NOT_RESURFACE]\n\n**Action Items:**\n- [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD]\n\n**Supersedes:** [DATE of previous decision on same topic, if any]\n**Superseded by:** [Filled in retroactively if overridden later]\n**Raw transcript:** memory\u002Fboard-meetings\u002F[DATE]-raw.md\n```\n\n---\n\n## Conflict Detection\n\nBefore logging, Chief of Staff checks for:\n1. **DO_NOT_RESURFACE violations** — new decision matches a rejected proposal\n2. **Topic contradictions** — two active decisions on same topic with different conclusions\n3. **Owner conflicts** — same action assigned to different people in different decisions\n\nWhen a conflict is found:\n```\n⚠️ DECISION CONFLICT\nNew: [text]\nConflicts with: [DATE] — [existing text]\n\nOptions: (1) Supersede old  (2) Merge  (3) Defer to founder\n```\n\n**DO_NOT_RESURFACE enforcement:**\n```\n? BLOCKED: \"[Proposal]\" was rejected on [DATE]. Reason: [reason].\nTo reopen: founder must explicitly say \"reopen [topic] from [DATE]\".\n```\n\n---\n\n## Logging Workflow (Post Phase 5)\n\n1. Founder approves synthesis\n2. Write Layer 1 raw transcript → `YYYY-MM-DD-raw.md`\n3. Check conflicts against `decisions.md`\n4. Surface conflicts → wait for founder resolution\n5. Append approved entries to `decisions.md`\n6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added\n\n---\n\n## Marking Actions Complete\n\n```markdown\n- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]\n```\n\nNever delete completed items. The history is the record.\n\n---\n\n## File Structure\n\n```\nmemory\u002Fboard-meetings\u002F\n├── decisions.md       # Layer 2: append-only, founder-approved\n├── YYYY-MM-DD-raw.md  # Layer 1: full transcript per meeting\n└── archive\u002FYYYY\u002F      # Raw files after 90 days\n```\n\n---\n\n## References\n- `templates\u002Fdecision-entry.md` — single entry template with field rules\n- `scripts\u002Fdecision_tracker.py` — CLI parser, overdue tracker, conflict detector\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":54,"python-tools":55},"Md Faiz Alam","decision-memory",1772668800000,"1.0.0","c-level","scripts\u002Fdecision_tracker.py","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","c-level-advisor\u002Fdecision-logger",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 decision-logger",{"tool":70,"command":71},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill decision-logger",{"tool":73,"command":74},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill decision-logger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fdecision-logger\u002FSKILL.md",true,[78,83],{"path":55,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"SCRIPT","脚本",23369,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fdecision-logger\u002Fscripts\u002Fdecision_tracker.py",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"templates\u002Fdecision-entry.md","REFERENCE","参考文档",2286,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fdecision-logger\u002Ftemplates\u002Fdecision-entry.md",[90,120,145,170,200,219],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":101,"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",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[102,103,104,105,106,107,108,109,37,110,111,112,113,114,115,116,117,118,119,28],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","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,109,37,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,37,161,162,163,164,165,166,167,168,169,28],"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":182,"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,179],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":180,"categoryName":181,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000032","设计师",[183,184,169,185,186,187,188,189,190,37,191,192,193,194,195,196,197,198,28,199],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"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",[206],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[208,184,169,36,209,210,211,212,102,213,190,214,153,215,216,217,136,195,28,218],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":230,"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",[225,228,229],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[231,232,184,169,36,233,234,106,190,235,236,237,238,239,137,240,241,242,243,28],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]