[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CDXB93CD2H4K88VF8RK6D":3,"skill-same:01M75CDXB93CD2H4K88VF8RK6D":65},{"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":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":35,"updatedAt":36,"install":37,"resources":50},"01M75CDXB93CD2H4K88VF8RK6D","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.","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\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","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository","https:\u002F\u002Fgithub.com\u002FAdmiralGallade","Eager to learn!\r\nI'll do anything for more knowledge anywhere.","2026-06-06 07:34:31",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill board-meeting",{"tool":43,"command":44},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill board-meeting",{"tool":46,"command":47},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill board-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fmeeting-facilitation.md","REFERENCE","参考文档",8212,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Freferences\u002Fmeeting-facilitation.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"templates\u002Fmeeting-agenda.md",1976,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-agenda.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"templates\u002Fmeeting-minutes.md",2465,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-minutes.md",[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75JSM6WGJ71BTHM6VC8CJ1X","verify-sign","Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75JSDSTP77TFM3JFGBB8QKP","template-usage","Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Ftemplate-usage\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75JS76Q2KC8PD598H2DZZRA","sign-artifact","Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build\u002Fpush; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsign-artifact\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75JS16EEFFHA44EBNE8KWNT","sei-analytics","Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsei-analytics\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M75JRWE3X3E7V9JFQ4ENZYZM","security-report","Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says \"security report\", \"vulnerabilities\", \"SBOM\", \"security scan\", \"compliance check\", or asks about application security.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsecurity-report\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M75JRSFJSNZFZRFKX8MSPCS2","scorecard-review","Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says \"scorecard\", \"service maturity\", \"production readiness\", \"compliance score\", or asks about service health scores.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fscorecard-review\u002FSKILL.md",[],[]]