Executive team perspectives for any codebase. Thirteen specialized review commands plus a single-CxO router (/ask) that analyze your project from different leadership viewpoints.
📝 Read the story (JP): Claude Codeに「経営会議」を持ち込む — claude-c-suite-plugin を作った話
/plugin marketplace add JFK/claude-c-suite-plugin
/plugin install claude-c-suiteThen in any git repository:
/claude-c-suite:ceo
The CEO command auto-diagnoses your project, picks the 3 most relevant
executive perspectives, and gives you a prioritized action list. When
in doubt, start with /ceo — it's the safe, always-correct entry point.
For the full guide (decision tree, common patterns, multi-role consultation, plugin combinations, troubleshooting), see USAGE.md (日本語版).
| Command | Role | What it reviews |
|---|---|---|
/ceo |
CEO (Meta) | Triages needs to the right CxOs, synthesizes cross-cutting insights |
/ask |
C-Suite Router | Auto-routes your question to the single best CxO and answers from that one lens |
/cto |
Chief Technology Officer | Tech debt, architecture, refactoring priorities, dependency risks |
/pm |
Product Manager | Milestone triage, issue prioritization, release planning |
/cdo |
Chief Design Officer | UI/UX consistency, design system health, component reuse |
/cso |
Chief Security Officer | Vulnerabilities, auth patterns, secret management, OWASP Top 10 |
/clo |
Chief Legal Officer | License compliance, data privacy, regulatory readiness, IP protection |
/coo |
Chief Operating Officer | CI/CD pipelines, deployment strategy, observability, incident readiness |
/cmo |
Chief Marketing Officer | SEO health, Core Web Vitals, social sharing, analytics implementation |
/caio |
Chief AI Officer | AI/ML governance, model lifecycle, responsible AI, LLM integration patterns |
/cfo |
Chief Financial Officer | Cloud cost optimization, resource efficiency, billing logic, compute waste |
/cio |
Chief Information Officer | Data governance, system integration, information architecture, schema management |
/qa-lead |
QA Lead | Test coverage, quality metrics, testing strategy gaps |
/dx-lead |
DX Lead | Developer experience, API ergonomics, SDK usability, onboarding |
/config |
Utility | Manage ~/.claude/claude-c-suite.json — show, init, read settings |
/audit |
Utility | Conformance audit and release gate |
- CEO — Sits above the cross-reference graph, not inside it. Triages the user's need to the 3 most relevant CxO perspectives, analyzes through those lenses, and synthesizes a unified executive decision. Does not perform specialized analysis — knows which experts to consult and how to resolve conflicts between them. "The right 3 perspectives beat all 11 spread thin"
/ask(Router) — The lightweight cousin of/ceo. Auto-routes a single question to the one best-fit CxO/Lead and answers from that single lens. Use it when you have a question but don't want to think about which expert to call. Cheaper than/ceo(one lens vs three) and easier than calling a role directly (no org-chart memorization). Declines routing and redirects to/ceowhen the question genuinely needs synthesis. "One sharp lens beats three blurry ones"
- CTO — Guards codebase health. Identifies tech debt that compounds over time, evaluates architecture decisions, and prioritizes refactoring. "Debt compounds"
- PM — Steers the ship to release. Triages milestones, orders issues by impact, and ensures bugs are fixed before features ship. "Bugs before features"
- CFO — Hunts down waste. Finds N+1 queries, idle resources, missing caches, and audits billing logic for correctness. "Every query has a price tag"
- CIO — Governs information architecture. Reviews data models, schema health, migration safety, system integration contracts, and data lifecycle. "Schema is the contract between past and future"
- CSO — Thinks like an attacker. Audits auth flows, scans for hardcoded secrets, checks dependencies against OWASP Top 10. "Secrets are toxic"
- CLO — Eliminates legal exposure. Maps dependency license trees for copyleft conflicts, assesses GDPR/CCPA readiness, and verifies IP provenance. "Licenses are viral"
- CDO — Enforces design consistency. Reviews component reuse, design token adherence, and UX coherence across the app. "Components are contracts"
- CMO — Makes the product discoverable. Checks SEO fundamentals, Core Web Vitals, OGP/social sharing, and analytics instrumentation. "Speed is conversion"
- COO — Keeps production running. Audits CI/CD pipelines, deployment strategies, observability coverage, and incident readiness. "Deploys should be boring"
- CAIO — Governs AI responsibly. Reviews model lifecycle, prompt engineering quality, bias detection, eval suites, and guardrails. "Prompts are production code"
- QA Lead — Closes testing gaps. Measures coverage, identifies missing test scenarios, and evaluates the testing strategy holistically. "Every bug is a missing test"
- DX Lead — Champions developer happiness. Reviews API ergonomics, error messages, SDK usability, and onboarding friction. "Pit of success"
/plugin marketplace add JFK/claude-c-suite-plugin
/plugin install claude-c-suiteThe plugin issues gh commands to read issues, milestones, and labels.
Most commands are read-only; /pm is the only command that may suggest
write operations (gh issue create, gh issue edit), and only after
explicit user confirmation.
| Use case | Recommended scopes |
|---|---|
| Public repos only | public_repo |
| Private repos | repo |
| Organization repos | repo + read:org |
See SECURITY.md for the full threat model and the vulnerability reporting process.
/claude-c-suite:ceo # Auto-diagnose and executive summary
/claude-c-suite:cto # Full CTO review of current repo
/claude-c-suite:cto debt # Focus on tech debt only
/claude-c-suite:cso auth # Focus on authentication
/claude-c-suite:clo licenses # Focus on dependency licenses
/claude-c-suite:coo cicd # Focus on CI/CD pipeline
/claude-c-suite:cmo seo # Focus on SEO health
/claude-c-suite:caio models # Focus on model lifecycle
/claude-c-suite:cfo costs # Focus on cloud costs
/claude-c-suite:cio data # Focus on data governance
Each role answers natural-language questions from its perspective, grounded in your actual codebase:
/claude-c-suite:ask Is this SQL schema normalized correctly?
/claude-c-suite:ask How risky is the new dependency we just added?
/claude-c-suite:ceo Are we ready to launch?
/claude-c-suite:cto Should we migrate to a monorepo?
/claude-c-suite:pm Should we delay the launch to fix these bugs?
/claude-c-suite:cso Is our JWT implementation secure?
/claude-c-suite:clo Can we use this GPL library in our SaaS product?
/claude-c-suite:cfo Are we over-provisioned on our database tier?
/claude-c-suite:caio Are we handling prompt injection risks?
Each role cross-references its Top 3 collaborators — the 3 roles it works most closely with. The CEO sits above as a meta-layer, reading the graph to select the right perspectives for any given need.
┌──────────────────────────────────────────────────────────┐
│ CEO (Meta-Layer) │
│ Reads the graph. Selects 3 perspectives per need. │
│ Synthesizes cross-cutting executive decisions. │
└────────────────────────────┬─────────────────────────────┘
│
─────────────────────── CxO Level ─────────────────────────
Tech×Security×Data Strategy Hub AI×Security×Cost
┌─────┐ ┌──────┐
│ CIO │◀──┐ ┌──────┐ ┌────▶│ CAIO │
└──┬──┘ │ ┌────▶│ PM │◀──┐ │ └──┬───┘
│ │ │ └──────┘ │ │ │
▼ │ │ │ │ ▼
┌─────┐ │ ┌─┴────┐ ┌───┴─┴─┐ ┌──────┐
│ CSO │◀──┼─▶│ CTO │ │ CFO │◀▶│ COO │
└──┬──┘ │ └──┬───┘ └───────┘ └──┬───┘
│ │ │ │
▼ │ ▼ Design×Marketing×DX ▼
┌─────┐ │ ┌─────┐ ┌─────┐ ┌────────┐
│ CLO │◀──┘ │ CDO │◀─▶│ CMO │ │QA Lead │
└─────┘ └──┬──┘ └──┬──┘ └────────┘
│ │
▼ ▼
┌─────────────┐
│ DX Lead │
└─────────────┘
─────────────────────── Lead Level ────────────────────────
| Officer | Top 3 Collaborators | Cluster |
|---|---|---|
| CTO | PM, CSO, CIO | Strategy hub |
| PM | CTO, CFO, COO | Strategy × Operations |
| CDO | CTO, CMO, DX Lead | Design × Marketing × DX |
| CSO | CTO, CLO, CAIO | Security × Legal × AI |
| CLO | CSO, CIO, PM | Legal × Data × Strategy |
| COO | CTO, QA Lead, CFO | Ops × Quality × Cost |
| CMO | CDO, CTO, DX Lead | Marketing × Design × DX |
| CAIO | CTO, CSO, CFO | AI × Security × Cost |
| CFO | CTO, CAIO, COO | Cost × AI × Ops |
| CIO | CTO, CSO, CLO | Data × Security × Legal |
| QA Lead | CTO, COO, CSO | Quality × Ops × Security |
| DX Lead | CTO, CDO, CMO | DX × Design × Marketing |
All officers also cross-reference PhD Panel findings when available.
graph TD
CEO["🏢 CEO<br/>(Meta-Layer)"]
CEO -.->|selects 3| CTO & PM & CSO & CIO & CDO & COO & CMO & CAIO & CFO & CLO & QA & DX
subgraph Strategy["Strategy Hub"]
CTO["CTO"] <--> PM["PM"]
end
subgraph TechSecData["Tech × Security × Data"]
CTO <--> CSO["CSO"]
CTO <--> CIO["CIO"]
CSO <--> CIO
end
subgraph SecLegalAI["Security × Legal × AI"]
CSO <--> CLO["CLO"]
CSO <--> CAIO["CAIO"]
CLO <--> CIO
end
subgraph AISecCost["AI × Security × Cost"]
CAIO <--> CFO["CFO"]
end
subgraph OpsQualCost["Ops × Quality × Cost"]
COO["COO"] <--> QA["QA Lead"]
COO <--> CFO
CTO <--> COO
end
subgraph DesignMktgDX["Design × Marketing × DX"]
CDO["CDO"] <--> CMO["CMO"]
CDO <--> DX["DX Lead"]
CMO <--> DX
end
PM <--> CFO
PM <--> COO
PM <--> CLO
CTO <--> CDO
CTO <--> CAIO
CTO <--> CFO
QA <--> CSO
Set a default output language for all C-Suite commands via
~/.claude/claude-c-suite.json:
/claude-c-suite:config init # creates the templateThen edit to your preference:
{
"version": "1.5.0",
"language": "ja"
}| Key | Values | Default |
|---|---|---|
language |
ISO 639-1 code (en, ja, zh, ko, es, fr, de, …) |
Auto-detect from question |
version |
Plugin version stamp (informational) | Set by init |
- If the file is missing or malformed, commands silently fall back to auto-detecting the language from the user's question.
- Prose, explanations, and recommendations are translated; code blocks, file paths, CLI commands, and structural headings stay in English.
- Run
/claude-c-suite:configto see the current effective config.
- Analysis only — Commands recommend actions but never execute changes
- Cross-referencing — Run multiple commands in one session; they reference each other's findings
- GitHub-native — Uses
ghCLI to gather issues, milestones, and commit history - Universal — No project-specific assumptions; works with any codebase
| Document | Purpose |
|---|---|
| USAGE.md / USAGE.ja.md | Full usage guide — quick start, decision tree, patterns, troubleshooting |
| SECURITY.md | Threat model, mitigations, GitHub token scopes, vulnerability reporting |
| CONTRIBUTING.md | Style guide, feature freeze policy, PR workflow |
| CHANGELOG.md | Release history (v1.0 → present) |
| AUDIT.md | Conformance audit matrix and verifier (python3 scripts/audit.py) |
- claude-phd-panel — Academic review (Distributed Systems, Statistics, Database Theory, etc.). Findings are auto-incorporated by C-Suite commands when run in the same session.
- expert-craft — Create your own custom domain experts that integrate with C-Suite cross-references.
MIT