[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BWDQTDGFB23VQDA8VSCN9":3,"skill-same:01M75BWDQTDGFB23VQDA8VSCN9":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75BWDQTDGFB23VQDA8VSCN9","boardroom",null,"\u002Fcs:boardroom \u003Cbrief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fboardroom\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"boardroom\"\ndescription: \"\u002Fcs:boardroom \u003Cbrief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo.\"\n---\n\n# \u002Fcs:boardroom — Multi-Role Boardroom Deliberation\n\n**Command:** `\u002Fcs:boardroom \u003Cbrief-path>`\n\nRuns the `board-meeting` skill protocol across the C-suite for a single strategy brief. This is the **heart of the plugin** — the multi-role deliberation that gstack's review chain only approximates.\n\n## Pipeline Position\n\n```\n\u002Fcs:office-hours  →  \u002Fcs:brief  →  \u002Fcs:boardroom  →  \u002Fcs:decide  →  \u002Fcs:execute  →  \u002Fcs:post-mortem\n                                     ↑ you are here\n```\n\n## The 6 Phases (from board-meeting skill)\n\n### Phase 1 — Briefing\n- Chief of Staff distributes the brief to all advisors marked in **Affected Roles**.\n- Each advisor reads company-context.md + the brief.\n- No discussion yet.\n\n### Phase 2 — Independent Thinking (ISOLATION)\n- **Critical:** each advisor produces their position **independently**, without seeing others' positions.\n- This prevents groupthink and surfaces dissent.\n- Each writes: their voice's opening, recommendation, top 3 concerns, top 3 supports.\n\n### Phase 3 — Cross-Examination\n- Positions revealed simultaneously.\n- Each advisor critiques the others' positions on the dimensions they own:\n  - cs-cfo-advisor critiques the math\n  - cs-ciso-advisor critiques the risk\n  - cs-cpo-advisor critiques the JTBD\n  - cs-cmo-advisor critiques the positioning\n  - cs-cro-advisor critiques the revenue math\n  - etc.\n\n### Phase 4 — Devil's Advocate Pass\n- `executive-mentor\u002Fdevils-advocate` agent runs `\u002Fem:challenge` on the leading option.\n- Surfaces three concerns with severity ratings.\n\n### Phase 5 — Synthesis\n- Chief of Staff synthesizes: which option commands majority, what are unresolved dissents.\n- Produces the **board memo** with recommendation + dissent.\n\n### Phase 6 — Decision Hand-off\n- Memo is presented to the founder.\n- Founder accepts, modifies, or rejects.\n- Approved memo routes to `\u002Fcs:decide` for logging.\n\n## Output: Board Memo\n\nSaved to `~\u002F.claude\u002Fboardroom\u002FYYYY-MM-DD-\u003Cslug>.md`:\n\n```markdown\n# Board Memo: \u003Ctopic>\n**Date:** YYYY-MM-DD\n**Brief:** \u003Clink to \u002Fcs:brief file>\n**Status:** AWAITING FOUNDER DECISION | APPROVED | REJECTED\n\n## Question\n[One sentence from the brief]\n\n## Recommended Option\n**\u003COption name>** — chosen because \u003Csynthesis reasoning>\n\n## Vote Tally\n| Advisor | Vote | One-Sentence Reason |\n|---|---|---|\n| cs-ceo-advisor | A | \u003Creason> |\n| cs-cfo-advisor | A | \u003Creason> |\n| cs-cto-advisor | B | \u003Creason> |\n| ... | | |\n\n## Dissent\n- **\u003Cdissenter>:** \u003Cunresolved concern>\n\n## Devil's Advocate Concerns\n1. **CRITICAL** — \u003Cconcern> — Mitigation: \u003Cplan>\n2. **HIGH** — \u003Cconcern> — Mitigation: \u003Cplan>\n3. **MEDIUM** — \u003Cconcern> — Mitigation: \u003Cplan>\n\n## Success & Kill Criteria\n[Copied from brief, refined by the panel]\n\n## Recommended Decision Path\n- `\u002Fcs:decide` → log the decision\n- `\u002Fcs:execute` → 90-day plan\n- `\u002Fcs:cross-eval` → multi-model sanity check (optional, high-stakes)\n- `\u002Fcs:freeze N` → cooldown lock (optional, irreversible)\n```\n\n## Why Phase 2 Isolation Matters\n\nIf advisors see each other's positions before forming their own, they anchor. Phase 2 isolation is the single highest-leverage practice in the board-meeting protocol — it surfaces the dissents that sycophancy would have suppressed.\n\n## Why This Beats gstack's Review Chain\n\n| | gstack `\u002Fautoplan` | `\u002Fcs:boardroom` |\n|---|---|---|\n| Roles | CEO → design → eng (3) | Up to 10 C-roles |\n| Order | Sequential | Phase 2 isolation, then simultaneous |\n| Dissent capture | Implicit | Explicit dissent column |\n| Adversarial pass | No | Phase 4 devil's advocate |\n| Output | Reviewed plan | Voted memo with dissent + kill criteria |\n\n## Workflow\n\n1. Read brief from `~\u002F.claude\u002Fbriefs\u002F\u003Cfile>`\n2. Identify affected roles\n3. Invoke each cs-* advisor independently (Phase 2)\n4. Collect positions\n5. Run cross-examination round (Phase 3)\n6. Run `\u002Fem:challenge` on leading option (Phase 4)\n7. Synthesize memo (Phase 5)\n8. Hand off to founder (Phase 6)\n\n## Routing\n\n- `\u002Fcs:decide` — log approved memo\n- `\u002Fcs:cross-eval` — high-stakes second opinion\n- `\u002Fcs:freeze` — cooldown lock\n\n## Related\n\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md)\n- Skills: [`board-meeting`](..\u002F..\u002F..\u002Fskills\u002Fboard-meeting\u002FSKILL.md), [`executive-mentor`](..\u002F..\u002F..\u002Fexecutive-mentor\u002F)\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:boardroom — Multi-Role Boardroom Deliberation\n\n**Command:** `\u002Fcs:boardroom \u003Cbrief-path>`\n\nRuns the `board-meeting` skill protocol across the C-suite for a single strategy brief. This is the **heart of the plugin** — the multi-role deliberation that gstack's review chain only approximates.\n\n## Pipeline Position\n\n```\n\u002Fcs:office-hours  →  \u002Fcs:brief  →  \u002Fcs:boardroom  →  \u002Fcs:decide  →  \u002Fcs:execute  →  \u002Fcs:post-mortem\n                                     ↑ you are here\n```\n\n## The 6 Phases (from board-meeting skill)\n\n### Phase 1 — Briefing\n- Chief of Staff distributes the brief to all advisors marked in **Affected Roles**.\n- Each advisor reads company-context.md + the brief.\n- No discussion yet.\n\n### Phase 2 — Independent Thinking (ISOLATION)\n- **Critical:** each advisor produces their position **independently**, without seeing others' positions.\n- This prevents groupthink and surfaces dissent.\n- Each writes: their voice's opening, recommendation, top 3 concerns, top 3 supports.\n\n### Phase 3 — Cross-Examination\n- Positions revealed simultaneously.\n- Each advisor critiques the others' positions on the dimensions they own:\n  - cs-cfo-advisor critiques the math\n  - cs-ciso-advisor critiques the risk\n  - cs-cpo-advisor critiques the JTBD\n  - cs-cmo-advisor critiques the positioning\n  - cs-cro-advisor critiques the revenue math\n  - etc.\n\n### Phase 4 — Devil's Advocate Pass\n- `executive-mentor\u002Fdevils-advocate` agent runs `\u002Fem:challenge` on the leading option.\n- Surfaces three concerns with severity ratings.\n\n### Phase 5 — Synthesis\n- Chief of Staff synthesizes: which option commands majority, what are unresolved dissents.\n- Produces the **board memo** with recommendation + dissent.\n\n### Phase 6 — Decision Hand-off\n- Memo is presented to the founder.\n- Founder accepts, modifies, or rejects.\n- Approved memo routes to `\u002Fcs:decide` for logging.\n\n## Output: Board Memo\n\nSaved to `~\u002F.claude\u002Fboardroom\u002FYYYY-MM-DD-\u003Cslug>.md`:\n\n```markdown\n# Board Memo: \u003Ctopic>\n**Date:** YYYY-MM-DD\n**Brief:** \u003Clink to \u002Fcs:brief file>\n**Status:** AWAITING FOUNDER DECISION | APPROVED | REJECTED\n\n## Question\n[One sentence from the brief]\n\n## Recommended Option\n**\u003COption name>** — chosen because \u003Csynthesis reasoning>\n\n## Vote Tally\n| Advisor | Vote | One-Sentence Reason |\n|---|---|---|\n| cs-ceo-advisor | A | \u003Creason> |\n| cs-cfo-advisor | A | \u003Creason> |\n| cs-cto-advisor | B | \u003Creason> |\n| ... | | |\n\n## Dissent\n- **\u003Cdissenter>:** \u003Cunresolved concern>\n\n## Devil's Advocate Concerns\n1. **CRITICAL** — \u003Cconcern> — Mitigation: \u003Cplan>\n2. **HIGH** — \u003Cconcern> — Mitigation: \u003Cplan>\n3. **MEDIUM** — \u003Cconcern> — Mitigation: \u003Cplan>\n\n## Success & Kill Criteria\n[Copied from brief, refined by the panel]\n\n## Recommended Decision Path\n- `\u002Fcs:decide` → log the decision\n- `\u002Fcs:execute` → 90-day plan\n- `\u002Fcs:cross-eval` → multi-model sanity check (optional, high-stakes)\n- `\u002Fcs:freeze N` → cooldown lock (optional, irreversible)\n```\n\n## Why Phase 2 Isolation Matters\n\nIf advisors see each other's positions before forming their own, they anchor. Phase 2 isolation is the single highest-leverage practice in the board-meeting protocol — it surfaces the dissents that sycophancy would have suppressed.\n\n## Why This Beats gstack's Review Chain\n\n| | gstack `\u002Fautoplan` | `\u002Fcs:boardroom` |\n|---|---|---|\n| Roles | CEO → design → eng (3) | Up to 10 C-roles |\n| Order | Sequential | Phase 2 isolation, then simultaneous |\n| Dissent capture | Implicit | Explicit dissent column |\n| Adversarial pass | No | Phase 4 devil's advocate |\n| Output | Reviewed plan | Voted memo with dissent + kill criteria |\n\n## Workflow\n\n1. Read brief from `~\u002F.claude\u002Fbriefs\u002F\u003Cfile>`\n2. Identify affected roles\n3. Invoke each cs-* advisor independently (Phase 2)\n4. Collect positions\n5. Run cross-examination round (Phase 3)\n6. Run `\u002Fem:challenge` on leading option (Phase 4)\n7. Synthesize memo (Phase 5)\n8. Hand off to founder (Phase 6)\n\n## Routing\n\n- `\u002Fcs:decide` — log approved memo\n- `\u002Fcs:cross-eval` — high-stakes second opinion\n- `\u002Fcs:freeze` — cooldown lock\n\n## Related\n\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md)\n- Skills: [`board-meeting`](..\u002F..\u002F..\u002Fskills\u002Fboard-meeting\u002FSKILL.md), [`executive-mentor`](..\u002F..\u002F..\u002Fexecutive-mentor\u002F)\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fboardroom",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill boardroom",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill boardroom",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill boardroom","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fboardroom\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]