agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use for /c-level-agents:boardroom, or a decision spanning several executive domains (a pricing change, raise vs cut). Runs a 6-phase C-suite deliberation and writes a board memo.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill boardroom --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill boardroom -a windsurf -y
name: "boardroom" description: "Use for /c-level-agents:boardroom, or a decision spanning several executive domains (a pricing change, raise vs cut). Runs a 6-phase C-suite deliberation and writes a board memo."
**Command:** `/c-level-agents:boardroom <brief-path>`
Runs 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.
/c-level-agents:office-hours → /c-level-agents:brief → /c-level-agents:boardroom → /c-level-agents:decide → /c-level-agents:execute → /c-level-agents:post-mortem
↑ you are hereSaved to `~/.claude/boardroom/YYYY-MM-DD-<slug>.md`:
# Board Memo: <topic> **Date:** YYYY-MM-DD **Brief:** <link to /c-level-agents:brief file> **Status:** AWAITING FOUNDER DECISION | APPROVED | REJECTED ## Question [One sentence from the brief] ## Recommended Option **<Option name>** — chosen because <synthesis reasoning> ## Vote Tally | Advisor | Vote | One-Sentence Reason | |---|---|---| | cs-ceo-advisor | A | <reason> | | cs-cfo-advisor | A | <reason> | | cs-cto-advisor | B | <reason> | | ... | | | ## Dissent - **<dissenter>:** <unresolved concern> ## Devil's Advocate Concerns 1. **CRITICAL** — <concern> — Mitigation: <plan> 2. **HIGH** — <concern> — Mitigation: <plan> 3. **MEDIUM** — <concern> — Mitigation: <plan> ## Success & Kill Criteria [Copied from brief, refined by the panel] ## Recommended Decision Path - `/c-level-agents:decide` → log the decision - `/c-level-agents:execute` → 90-day plan - `/c-level-agents:cross-eval` → multi-model sanity check (optional, high-stakes) - `/c-level-agents:freeze N` → cooldown lock (optional, irreversible)
If 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.
| | gstack `/autoplan` | `/c-level-agents:boardroom` | |---|---|---| | Roles | CEO → design → eng (3) | Up to 10 C-roles | | Order | Sequential | Phase 2 isolation, then simultaneous | | Dissent capture | Implicit | Explicit dissent column | | Adversarial pass | No | Phase 4 devil's advocate | | Output | Reviewed plan | Voted memo with dissent + kill criteria |
1. Read brief from `~/.claude/briefs/<file>` 2. Identify affected roles 3. Invoke each cs-* advisor independently (Phase 2) 4. Collect positions 5. Run cross-examination round (Phase 3) 6. Run `/executive-mentor:challenge` on leading option (Phase 4) 7. Synthesize memo (Phase 5) 8. Hand off to founder (Phase 6)
---
**Version:** 1.0.0
411 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…