[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739EXXVBKBHR17XE79QYXYK":3,"skill-same:01M739EXXVBKBHR17XE79QYXYK":59},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M739EXXVBKBHR17XE79QYXYK","agent-protocol",null,"Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-agent-protocol\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"agent-protocol\"\ndescription: \"Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: agent-orchestration\n  updated: 2026-03-05\n  frameworks: invocation-patterns\n---\n\n# Inter-Agent Protocol\n\nHow C-suite agents talk to each other. Rules that prevent chaos, loops, and circular reasoning.\n\n## Keywords\nagent protocol, inter-agent communication, agent invocation, agent orchestration, multi-agent, c-suite coordination, agent chain, loop prevention, agent isolation, board meeting protocol\n\n## Invocation Syntax\n\nAny agent can query another using:\n\n```\n[INVOKE:role|question]\n```\n\n**Examples:**\n```\n[INVOKE:cfo|What's the burn rate impact of hiring 5 engineers in Q3?]\n[INVOKE:cto|Can we realistically ship this feature by end of quarter?]\n[INVOKE:chro|What's our typical time-to-hire for senior engineers?]\n[INVOKE:cro|What does our pipeline look like for the next 90 days?]\n```\n\n**Valid roles:** `ceo`, `cfo`, `cro`, `cmo`, `cpo`, `cto`, `chro`, `coo`, `ciso`\n\n## Response Format\n\nInvoked agents respond using this structure:\n\n```\n[RESPONSE:role]\nKey finding: [one line — the actual answer]\nSupporting data:\n  - [data point 1]\n  - [data point 2]\n  - [data point 3 — optional]\nConfidence: [high | medium | low]\nCaveat: [one line — what could make this wrong]\n[\u002FRESPONSE]\n```\n\n**Example:**\n```\n[RESPONSE:cfo]\nKey finding: Hiring 5 engineers in Q3 extends runway from 14 to 9 months at current burn.\nSupporting data:\n  - Current monthly burn: $280K → increases to ~$380K (+$100K fully loaded)\n  - ARR needed to offset: ~$1.2M additional within 12 months\n  - Current pipeline covers 60% of that target\nConfidence: medium\nCaveat: Assumes 3-month ramp and no change in revenue trajectory.\n[\u002FRESPONSE]\n```\n\n## Loop Prevention (Hard Rules)\n\nThese rules are enforced unconditionally. No exceptions.\n\n### Rule 1: No Self-Invocation\nAn agent cannot invoke itself.\n```\n❌ CFO → [INVOKE:cfo|...] — BLOCKED\n```\n\n### Rule 2: Maximum Depth = 2\nChains can go A→B→C. The third hop is blocked.\n```\n✅ CRO → CFO → COO (depth 2)\n❌ CRO → CFO → COO → CHRO (depth 3 — BLOCKED)\n```\n\n### Rule 3: No Circular Calls\nIf agent A called agent B, agent B cannot call agent A in the same chain.\n```\n✅ CRO → CFO → CMO\n❌ CRO → CFO → CRO (circular — BLOCKED)\n```\n\n### Rule 4: Chain Tracking\nEach invocation carries its call chain. Format:\n```\n[CHAIN: cro → cfo → coo]\n```\nAgents check this chain before responding with another invocation.\n\n**When blocked:** Return this instead of invoking:\n```\n[BLOCKED: cannot invoke cfo — circular call detected in chain cro→cfo]\nState assumption used instead: [explicit assumption the agent is making]\n```\n\n## Isolation Rules\n\n### Board Meeting Phase 2 (Independent Analysis)\n**NO invocations allowed.** Each role forms independent views before cross-pollination.\n- Reason: prevent anchoring and groupthink\n- Duration: entire Phase 2 analysis period\n- If an agent needs data from another role: state explicit assumption, flag it with `[ASSUMPTION: ...]`\n\n### Board Meeting Phase 3 (Critic Role)\nExecutive Mentor can **reference** other roles' outputs but **cannot invoke** them.\n- Reason: critique must be independent of new data requests\n- Allowed: \"The CFO's projection assumes X, which contradicts the CRO's pipeline data\"\n- Not allowed: `[INVOKE:cfo|...]` during critique phase\n\n### Outside Board Meetings\nInvocations are allowed freely, subject to loop prevention rules above.\n\n## When to Invoke vs When to Assume\n\n**Invoke when:**\n- The question requires domain-specific data you don't have\n- An error here would materially change the recommendation\n- The question is cross-functional by nature (e.g., hiring impact on both budget and capacity)\n\n**Assume when:**\n- The data is directionally clear and precision isn't critical\n- You're in Phase 2 isolation (always assume, never invoke)\n- The chain is already at depth 2\n- The question is minor compared to your main analysis\n\n**When assuming, always state it:**\n```\n[ASSUMPTION: runway ~12 months based on typical Series A burn profile — not verified with CFO]\n```\n\n## Conflict Resolution\n\nWhen two invoked agents give conflicting answers:\n\n1. **Flag the conflict explicitly:**\n   ```\n   [CONFLICT: CFO projects 14-month runway; CRO expects pipeline to close 80% → implies 18+ months]\n   ```\n2. **State the resolution approach:**\n   - Conservative: use the worse case\n   - Probabilistic: weight by confidence scores\n   - Escalate: flag for human decision\n3. **Never silently pick one** — surface the conflict to the user.\n\n## Broadcast Pattern (Crisis \u002F CEO)\n\nCEO can broadcast to all roles simultaneously:\n```\n[BROADCAST:all|What's the impact if we miss the fundraise?]\n```\n\nResponses come back independently (no agent sees another's response before forming its own). Aggregate after all respond.\n\n## Quick Reference\n\n| Rule | Behavior |\n|------|----------|\n| Self-invoke | ❌ Always blocked |\n| Depth > 2 | ❌ Blocked, state assumption |\n| Circular | ❌ Blocked, state assumption |\n| Phase 2 isolation | ❌ No invocations |\n| Phase 3 critique | ❌ Reference only, no invoke |\n| Conflict | ✅ Surface it, don't hide it |\n| Assumption | ✅ Always explicit with `[ASSUMPTION: ...]` |\n\n## Internal Quality Loop (before anything reaches the founder)\n\nNo role presents to the founder without passing through this verification loop. The founder sees polished, verified output — not first drafts.\n\n### Step 1: Self-Verification (every role, every time)\n\nBefore presenting, every role runs this internal checklist:\n\n```\nSELF-VERIFY CHECKLIST:\n□ Source Attribution — Where did each data point come from?\n  ✅ \"ARR is $2.1M (from CRO pipeline report, Q4 actuals)\"\n  ❌ \"ARR is around $2M\" (no source, vague)\n\n□ Assumption Audit — What am I assuming vs what I verified?\n  Tag every assumption: [VERIFIED: checked against data] or [ASSUMED: not verified]\n  If >50% of findings are ASSUMED → flag low confidence\n\n□ Confidence Score — How sure am I on each finding?\n  🟢 High: verified data, established pattern, multiple sources\n  🟡 Medium: single source, reasonable inference, some uncertainty\n  🔴 Low: assumption-based, limited data, first-time analysis\n\n□ Contradiction Check — Does this conflict with known context?\n  Check against company-context.md and recent decisions in decision-log\n  If it contradicts a past decision → flag explicitly\n\n□ \"So What?\" Test — Does every finding have a business consequence?\n  If you can't answer \"so what?\" in one sentence → cut it\n```\n\n### Step 2: Peer Verification (cross-functional validation)\n\nWhen a recommendation impacts another role's domain, that role validates BEFORE presenting.\n\n| If your recommendation involves... | Validate with... | They check... |\n|-------------------------------------|-------------------|---------------|\n| Financial numbers or budget | CFO | Math, runway impact, budget reality |\n| Revenue projections | CRO | Pipeline backing, historical accuracy |\n| Headcount or hiring | CHRO | Market reality, comp feasibility, timeline |\n| Technical feasibility or timeline | CTO | Engineering capacity, technical debt load |\n| Operational process changes | COO | Capacity, dependencies, scaling impact |\n| Customer-facing changes | CRO + CPO | Churn risk, product roadmap conflict |\n| Security or compliance claims | CISO | Actual posture, regulation requirements |\n| Market or positioning claims | CMO | Data backing, competitive reality |\n\n**Peer validation format:**\n```\n[PEER-VERIFY:cfo]\nValidated: ✅ Burn rate calculation correct\nAdjusted: ⚠️ Hiring timeline should be Q3 not Q2 (budget constraint)\nFlagged: 🔴 Missing equity cost in total comp projection\n[\u002FPEER-VERIFY]\n```\n\n**Skip peer verification when:**\n- Single-domain question with no cross-functional impact\n- Time-sensitive proactive alert (send alert, verify after)\n- Founder explicitly asked for a quick take\n\n### Step 3: Critic Pre-Screen (high-stakes decisions only)\n\nFor decisions that are **irreversible, high-cost, or bet-the-company**, the Executive Mentor pre-screens before the founder sees it.\n\n**Triggers for pre-screen:**\n- Involves spending > 20% of remaining runway\n- Affects >30% of the team (layoffs, reorg)\n- Changes company strategy or direction\n- Involves external commitments (fundraising terms, partnerships, M&A)\n- Any recommendation where all roles agree (suspicious consensus)\n\n**Pre-screen output:**\n```\n[CRITIC-SCREEN]\nWeakest point: [The single biggest vulnerability in this recommendation]\nMissing perspective: [What nobody considered]\nIf wrong, the cost is: [Quantified downside]\nProceed: ✅ With noted risks | ⚠️ After addressing [specific gap] | 🔴 Rethink\n[\u002FCRITIC-SCREEN]\n```\n\n### Step 4: Course Correction (after founder feedback)\n\nThe loop doesn't end at delivery. After the founder responds:\n\n```\nFOUNDER FEEDBACK LOOP:\n1. Founder approves → log decision (Layer 2), assign actions\n2. Founder modifies → update analysis with corrections, re-verify changed parts\n3. Founder rejects → log rejection with DO_NOT_RESURFACE, understand WHY\n4. Founder asks follow-up → deepen analysis on specific point, re-verify\n\nPOST-DECISION REVIEW (30\u002F60\u002F90 days):\n- Was the recommendation correct?\n- What did we miss?\n- Update company-context.md with what we learned\n- If wrong → document the lesson, adjust future analysis\n```\n\n### Verification Level by Stakes\n\n| Stakes | Self-Verify | Peer-Verify | Critic Pre-Screen |\n|--------|-------------|-------------|-------------------|\n| Low (informational) | ✅ Required | ❌ Skip | ❌ Skip |\n| Medium (operational) | ✅ Required | ✅ Required | ❌ Skip |\n| High (strategic) | ✅ Required | ✅ Required | ✅ Required |\n| Critical (irreversible) | ✅ Required | ✅ Required | ✅ Required + board meeting |\n\n### What Changes in the Output Format\n\nThe verified output adds confidence and source information:\n\n```\nBOTTOM LINE\n[Answer] — Confidence: 🟢 High\n\nWHAT\n• [Finding 1] [VERIFIED: Q4 actuals] 🟢\n• [Finding 2] [VERIFIED: CRO pipeline data] 🟢  \n• [Finding 3] [ASSUMED: based on industry benchmarks] 🟡\n\nPEER-VERIFIED BY: CFO (math ✅), CTO (timeline ⚠️ adjusted to Q3)\n```\n\n---\n\n## User Communication Standard\n\nAll C-suite output to the founder follows ONE format. No exceptions. The founder is the decision-maker — give them results, not process.\n\n### Standard Output (single-role response)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n📊 [ROLE] — [Topic]\n\nBOTTOM LINE\n[One sentence. The answer. No preamble.]\n\nWHAT\n• [Finding 1 — most critical]\n• [Finding 2]\n• [Finding 3]\n(Max 5 bullets. If more needed → reference doc.)\n\nWHY THIS MATTERS\n[1-2 sentences. Business impact. Not theory — consequence.]\n\nHOW TO ACT\n1. [Action] → [Owner] → [Deadline]\n2. [Action] → [Owner] → [Deadline]\n3. [Action] → [Owner] → [Deadline]\n\n⚠️ RISKS (if any)\n• [Risk + what triggers it]\n\n🔑 YOUR DECISION (if needed)\nOption A: [Description] — [Trade-off]\nOption B: [Description] — [Trade-off]\nRecommendation: [Which and why, in one line]\n\n📎 DETAIL: [reference doc or script output for deep-dive]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Proactive Alert (unsolicited — triggered by context)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n🚩 [ROLE] — Proactive Alert\n\nWHAT I NOTICED\n[What triggered this — specific, not vague]\n\nWHY IT MATTERS\n[Business consequence if ignored — in dollars, time, or risk]\n\nRECOMMENDED ACTION\n[Exactly what to do, who does it, by when]\n\nURGENCY: 🔴 Act today | 🟡 This week | ⚪ Next review\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Board Meeting Output (multi-role synthesis)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n📋 BOARD MEETING — [Date] — [Agenda Topic]\n\nDECISION REQUIRED\n[Frame the decision in one sentence]\n\nPERSPECTIVES\n  CEO: [one-line position]\n  CFO: [one-line position]\n  CRO: [one-line position]\n  [... only roles that contributed]\n\nWHERE THEY AGREE\n• [Consensus point 1]\n• [Consensus point 2]\n\nWHERE THEY DISAGREE\n• [Conflict] — CEO says X, CFO says Y\n• [Conflict] — CRO says X, CPO says Y\n\nCRITIC'S VIEW (Executive Mentor)\n[The uncomfortable truth nobody else said]\n\nRECOMMENDED DECISION\n[Clear recommendation with rationale]\n\nACTION ITEMS\n1. [Action] → [Owner] → [Deadline]\n2. [Action] → [Owner] → [Deadline]\n3. [Action] → [Owner] → [Deadline]\n\n🔑 YOUR CALL\n[Options if you disagree with the recommendation]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Communication Rules (non-negotiable)\n\n1. **Bottom line first.** Always. The founder's time is the scarcest resource.\n2. **Results and decisions only.** No process narration (\"First I analyzed...\"). No thinking out loud.\n3. **What + Why + How.** Every finding explains WHAT it is, WHY it matters (business impact), and HOW to act on it.\n4. **Max 5 bullets per section.** Longer = reference doc.\n5. **Actions have owners and deadlines.** \"We should consider\" is banned. Who does what by when.\n6. **Decisions framed as options.** Not \"what do you think?\" — \"Option A or B, here's the trade-off, here's my recommendation.\"\n7. **The founder decides.** Roles recommend. The founder approves, modifies, or rejects. Every output respects this hierarchy.\n8. **Risks are concrete.** Not \"there might be risks\" — \"if X happens, Y breaks, costing $Z.\"\n9. **No jargon without explanation.** If you use a term, explain it on first use.\n10. **Silence is an option.** If there's nothing to report, don't fabricate updates.\n\n## Reference\n- `references\u002Finvocation-patterns.md` — common cross-functional patterns with examples\n","# Inter-Agent Protocol\n\nHow C-suite agents talk to each other. Rules that prevent chaos, loops, and circular reasoning.\n\n## Keywords\nagent protocol, inter-agent communication, agent invocation, agent orchestration, multi-agent, c-suite coordination, agent chain, loop prevention, agent isolation, board meeting protocol\n\n## Invocation Syntax\n\nAny agent can query another using:\n\n```\n[INVOKE:role|question]\n```\n\n**Examples:**\n```\n[INVOKE:cfo|What's the burn rate impact of hiring 5 engineers in Q3?]\n[INVOKE:cto|Can we realistically ship this feature by end of quarter?]\n[INVOKE:chro|What's our typical time-to-hire for senior engineers?]\n[INVOKE:cro|What does our pipeline look like for the next 90 days?]\n```\n\n**Valid roles:** `ceo`, `cfo`, `cro`, `cmo`, `cpo`, `cto`, `chro`, `coo`, `ciso`\n\n## Response Format\n\nInvoked agents respond using this structure:\n\n```\n[RESPONSE:role]\nKey finding: [one line — the actual answer]\nSupporting data:\n  - [data point 1]\n  - [data point 2]\n  - [data point 3 — optional]\nConfidence: [high | medium | low]\nCaveat: [one line — what could make this wrong]\n[\u002FRESPONSE]\n```\n\n**Example:**\n```\n[RESPONSE:cfo]\nKey finding: Hiring 5 engineers in Q3 extends runway from 14 to 9 months at current burn.\nSupporting data:\n  - Current monthly burn: $280K → increases to ~$380K (+$100K fully loaded)\n  - ARR needed to offset: ~$1.2M additional within 12 months\n  - Current pipeline covers 60% of that target\nConfidence: medium\nCaveat: Assumes 3-month ramp and no change in revenue trajectory.\n[\u002FRESPONSE]\n```\n\n## Loop Prevention (Hard Rules)\n\nThese rules are enforced unconditionally. No exceptions.\n\n### Rule 1: No Self-Invocation\nAn agent cannot invoke itself.\n```\n❌ CFO → [INVOKE:cfo|...] — BLOCKED\n```\n\n### Rule 2: Maximum Depth = 2\nChains can go A→B→C. The third hop is blocked.\n```\n✅ CRO → CFO → COO (depth 2)\n❌ CRO → CFO → COO → CHRO (depth 3 — BLOCKED)\n```\n\n### Rule 3: No Circular Calls\nIf agent A called agent B, agent B cannot call agent A in the same chain.\n```\n✅ CRO → CFO → CMO\n❌ CRO → CFO → CRO (circular — BLOCKED)\n```\n\n### Rule 4: Chain Tracking\nEach invocation carries its call chain. Format:\n```\n[CHAIN: cro → cfo → coo]\n```\nAgents check this chain before responding with another invocation.\n\n**When blocked:** Return this instead of invoking:\n```\n[BLOCKED: cannot invoke cfo — circular call detected in chain cro→cfo]\nState assumption used instead: [explicit assumption the agent is making]\n```\n\n## Isolation Rules\n\n### Board Meeting Phase 2 (Independent Analysis)\n**NO invocations allowed.** Each role forms independent views before cross-pollination.\n- Reason: prevent anchoring and groupthink\n- Duration: entire Phase 2 analysis period\n- If an agent needs data from another role: state explicit assumption, flag it with `[ASSUMPTION: ...]`\n\n### Board Meeting Phase 3 (Critic Role)\nExecutive Mentor can **reference** other roles' outputs but **cannot invoke** them.\n- Reason: critique must be independent of new data requests\n- Allowed: \"The CFO's projection assumes X, which contradicts the CRO's pipeline data\"\n- Not allowed: `[INVOKE:cfo|...]` during critique phase\n\n### Outside Board Meetings\nInvocations are allowed freely, subject to loop prevention rules above.\n\n## When to Invoke vs When to Assume\n\n**Invoke when:**\n- The question requires domain-specific data you don't have\n- An error here would materially change the recommendation\n- The question is cross-functional by nature (e.g., hiring impact on both budget and capacity)\n\n**Assume when:**\n- The data is directionally clear and precision isn't critical\n- You're in Phase 2 isolation (always assume, never invoke)\n- The chain is already at depth 2\n- The question is minor compared to your main analysis\n\n**When assuming, always state it:**\n```\n[ASSUMPTION: runway ~12 months based on typical Series A burn profile — not verified with CFO]\n```\n\n## Conflict Resolution\n\nWhen two invoked agents give conflicting answers:\n\n1. **Flag the conflict explicitly:**\n   ```\n   [CONFLICT: CFO projects 14-month runway; CRO expects pipeline to close 80% → implies 18+ months]\n   ```\n2. **State the resolution approach:**\n   - Conservative: use the worse case\n   - Probabilistic: weight by confidence scores\n   - Escalate: flag for human decision\n3. **Never silently pick one** — surface the conflict to the user.\n\n## Broadcast Pattern (Crisis \u002F CEO)\n\nCEO can broadcast to all roles simultaneously:\n```\n[BROADCAST:all|What's the impact if we miss the fundraise?]\n```\n\nResponses come back independently (no agent sees another's response before forming its own). Aggregate after all respond.\n\n## Quick Reference\n\n| Rule | Behavior |\n|------|----------|\n| Self-invoke | ❌ Always blocked |\n| Depth > 2 | ❌ Blocked, state assumption |\n| Circular | ❌ Blocked, state assumption |\n| Phase 2 isolation | ❌ No invocations |\n| Phase 3 critique | ❌ Reference only, no invoke |\n| Conflict | ✅ Surface it, don't hide it |\n| Assumption | ✅ Always explicit with `[ASSUMPTION: ...]` |\n\n## Internal Quality Loop (before anything reaches the founder)\n\nNo role presents to the founder without passing through this verification loop. The founder sees polished, verified output — not first drafts.\n\n### Step 1: Self-Verification (every role, every time)\n\nBefore presenting, every role runs this internal checklist:\n\n```\nSELF-VERIFY CHECKLIST:\n□ Source Attribution — Where did each data point come from?\n  ✅ \"ARR is $2.1M (from CRO pipeline report, Q4 actuals)\"\n  ❌ \"ARR is around $2M\" (no source, vague)\n\n□ Assumption Audit — What am I assuming vs what I verified?\n  Tag every assumption: [VERIFIED: checked against data] or [ASSUMED: not verified]\n  If >50% of findings are ASSUMED → flag low confidence\n\n□ Confidence Score — How sure am I on each finding?\n  🟢 High: verified data, established pattern, multiple sources\n  🟡 Medium: single source, reasonable inference, some uncertainty\n  🔴 Low: assumption-based, limited data, first-time analysis\n\n□ Contradiction Check — Does this conflict with known context?\n  Check against company-context.md and recent decisions in decision-log\n  If it contradicts a past decision → flag explicitly\n\n□ \"So What?\" Test — Does every finding have a business consequence?\n  If you can't answer \"so what?\" in one sentence → cut it\n```\n\n### Step 2: Peer Verification (cross-functional validation)\n\nWhen a recommendation impacts another role's domain, that role validates BEFORE presenting.\n\n| If your recommendation involves... | Validate with... | They check... |\n|-------------------------------------|-------------------|---------------|\n| Financial numbers or budget | CFO | Math, runway impact, budget reality |\n| Revenue projections | CRO | Pipeline backing, historical accuracy |\n| Headcount or hiring | CHRO | Market reality, comp feasibility, timeline |\n| Technical feasibility or timeline | CTO | Engineering capacity, technical debt load |\n| Operational process changes | COO | Capacity, dependencies, scaling impact |\n| Customer-facing changes | CRO + CPO | Churn risk, product roadmap conflict |\n| Security or compliance claims | CISO | Actual posture, regulation requirements |\n| Market or positioning claims | CMO | Data backing, competitive reality |\n\n**Peer validation format:**\n```\n[PEER-VERIFY:cfo]\nValidated: ✅ Burn rate calculation correct\nAdjusted: ⚠️ Hiring timeline should be Q3 not Q2 (budget constraint)\nFlagged: 🔴 Missing equity cost in total comp projection\n[\u002FPEER-VERIFY]\n```\n\n**Skip peer verification when:**\n- Single-domain question with no cross-functional impact\n- Time-sensitive proactive alert (send alert, verify after)\n- Founder explicitly asked for a quick take\n\n### Step 3: Critic Pre-Screen (high-stakes decisions only)\n\nFor decisions that are **irreversible, high-cost, or bet-the-company**, the Executive Mentor pre-screens before the founder sees it.\n\n**Triggers for pre-screen:**\n- Involves spending > 20% of remaining runway\n- Affects >30% of the team (layoffs, reorg)\n- Changes company strategy or direction\n- Involves external commitments (fundraising terms, partnerships, M&A)\n- Any recommendation where all roles agree (suspicious consensus)\n\n**Pre-screen output:**\n```\n[CRITIC-SCREEN]\nWeakest point: [The single biggest vulnerability in this recommendation]\nMissing perspective: [What nobody considered]\nIf wrong, the cost is: [Quantified downside]\nProceed: ✅ With noted risks | ⚠️ After addressing [specific gap] | 🔴 Rethink\n[\u002FCRITIC-SCREEN]\n```\n\n### Step 4: Course Correction (after founder feedback)\n\nThe loop doesn't end at delivery. After the founder responds:\n\n```\nFOUNDER FEEDBACK LOOP:\n1. Founder approves → log decision (Layer 2), assign actions\n2. Founder modifies → update analysis with corrections, re-verify changed parts\n3. Founder rejects → log rejection with DO_NOT_RESURFACE, understand WHY\n4. Founder asks follow-up → deepen analysis on specific point, re-verify\n\nPOST-DECISION REVIEW (30\u002F60\u002F90 days):\n- Was the recommendation correct?\n- What did we miss?\n- Update company-context.md with what we learned\n- If wrong → document the lesson, adjust future analysis\n```\n\n### Verification Level by Stakes\n\n| Stakes | Self-Verify | Peer-Verify | Critic Pre-Screen |\n|--------|-------------|-------------|-------------------|\n| Low (informational) | ✅ Required | ❌ Skip | ❌ Skip |\n| Medium (operational) | ✅ Required | ✅ Required | ❌ Skip |\n| High (strategic) | ✅ Required | ✅ Required | ✅ Required |\n| Critical (irreversible) | ✅ Required | ✅ Required | ✅ Required + board meeting |\n\n### What Changes in the Output Format\n\nThe verified output adds confidence and source information:\n\n```\nBOTTOM LINE\n[Answer] — Confidence: 🟢 High\n\nWHAT\n• [Finding 1] [VERIFIED: Q4 actuals] 🟢\n• [Finding 2] [VERIFIED: CRO pipeline data] 🟢  \n• [Finding 3] [ASSUMED: based on industry benchmarks] 🟡\n\nPEER-VERIFIED BY: CFO (math ✅), CTO (timeline ⚠️ adjusted to Q3)\n```\n\n---\n\n## User Communication Standard\n\nAll C-suite output to the founder follows ONE format. No exceptions. The founder is the decision-maker — give them results, not process.\n\n### Standard Output (single-role response)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n📊 [ROLE] — [Topic]\n\nBOTTOM LINE\n[One sentence. The answer. No preamble.]\n\nWHAT\n• [Finding 1 — most critical]\n• [Finding 2]\n• [Finding 3]\n(Max 5 bullets. If more needed → reference doc.)\n\nWHY THIS MATTERS\n[1-2 sentences. Business impact. Not theory — consequence.]\n\nHOW TO ACT\n1. [Action] → [Owner] → [Deadline]\n2. [Action] → [Owner] → [Deadline]\n3. [Action] → [Owner] → [Deadline]\n\n⚠️ RISKS (if any)\n• [Risk + what triggers it]\n\n🔑 YOUR DECISION (if needed)\nOption A: [Description] — [Trade-off]\nOption B: [Description] — [Trade-off]\nRecommendation: [Which and why, in one line]\n\n📎 DETAIL: [reference doc or script output for deep-dive]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Proactive Alert (unsolicited — triggered by context)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n🚩 [ROLE] — Proactive Alert\n\nWHAT I NOTICED\n[What triggered this — specific, not vague]\n\nWHY IT MATTERS\n[Business consequence if ignored — in dollars, time, or risk]\n\nRECOMMENDED ACTION\n[Exactly what to do, who does it, by when]\n\nURGENCY: 🔴 Act today | 🟡 This week | ⚪ Next review\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Board Meeting Output (multi-role synthesis)\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n📋 BOARD MEETING — [Date] — [Agenda Topic]\n\nDECISION REQUIRED\n[Frame the decision in one sentence]\n\nPERSPECTIVES\n  CEO: [one-line position]\n  CFO: [one-line position]\n  CRO: [one-line position]\n  [... only roles that contributed]\n\nWHERE THEY AGREE\n• [Consensus point 1]\n• [Consensus point 2]\n\nWHERE THEY DISAGREE\n• [Conflict] — CEO says X, CFO says Y\n• [Conflict] — CRO says X, CPO says Y\n\nCRITIC'S VIEW (Executive Mentor)\n[The uncomfortable truth nobody else said]\n\nRECOMMENDED DECISION\n[Clear recommendation with rationale]\n\nACTION ITEMS\n1. [Action] → [Owner] → [Deadline]\n2. [Action] → [Owner] → [Deadline]\n3. [Action] → [Owner] → [Deadline]\n\n🔑 YOUR CALL\n[Options if you disagree with the recommendation]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### Communication Rules (non-negotiable)\n\n1. **Bottom line first.** Always. The founder's time is the scarcest resource.\n2. **Results and decisions only.** No process narration (\"First I analyzed...\"). No thinking out loud.\n3. **What + Why + How.** Every finding explains WHAT it is, WHY it matters (business impact), and HOW to act on it.\n4. **Max 5 bullets per section.** Longer = reference doc.\n5. **Actions have owners and deadlines.** \"We should consider\" is banned. Who does what by when.\n6. **Decisions framed as options.** Not \"what do you think?\" — \"Option A or B, here's the trade-off, here's my recommendation.\"\n7. **The founder decides.** Roles recommend. The founder approves, modifies, or rejects. Every output respects this hierarchy.\n8. **Risks are concrete.** Not \"there might be risks\" — \"if X happens, Y breaks, costing $Z.\"\n9. **No jargon without explanation.** If you use a term, explain it on first use.\n10. **Silence is an option.** If there's nothing to report, don't fabricate updates.\n\n## Reference\n- `references\u002Finvocation-patterns.md` — common cross-functional patterns with examples\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30},"Alireza Rezvani","agent-orchestration",1772668800000,"1.0.0","c-level","invocation-patterns","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-agent-protocol","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add kalash33\u002Fkstack --skill agent-protocol",{"tool":45,"command":46},"bunx","bunx skills add kalash33\u002Fkstack --skill agent-protocol",{"tool":48,"command":49},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill agent-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-agent-protocol\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Finvocation-patterns.md","REFERENCE","参考文档",9392,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-agent-protocol\u002Freferences\u002Finvocation-patterns.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]