[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754MHQ06T6XTNFTQT8TF94F":3,"skill-same:01M754MHQ06T6XTNFTQT8TF94F":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":13,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M754MHQ06T6XTNFTQT8TF94F","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.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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: Alireza Rezvani\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":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29},"Alireza Rezvani","board-protocol",1772668800000,"1.0.0","c-level","6-phase-board, two-layer-memory, independent-contributions","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ASoudy\u002FAGS --skill board-meeting",{"tool":42,"command":43},"bunx","bunx skills add ASoudy\u002FAGS --skill board-meeting",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill board-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002FSKILL.md",true,[50,56,60],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fmeeting-facilitation.md","REFERENCE","参考文档",8212,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Freferences\u002Fmeeting-facilitation.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"templates\u002Fmeeting-agenda.md",1976,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-agenda.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"templates\u002Fmeeting-minutes.md",2465,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-minutes.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]