Claude C-Suite Plugin
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 を作った話
60-second quick start
/plugin marketplace add JFK/claude-c-suite-plugin
/plugin install claude-c-suite
Then 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.
Codex quick start
This repository also ships a Codex plugin manifest and skill adapters:
.codex-plugin/plugin.json and skills/.
Once installed in Codex, start a new thread in any git repository and use
the equivalent skill:
$claude-c-suite-ceo
You can also ask naturally:
Use Claude C-Suite CEO to review this repository.
$claude-c-suite-ask How risky is the new dependency we added?
For the full guide (decision tree, common patterns, multi-role
consultation, plugin combinations, troubleshooting), see
USAGE.md (日本語版).
Commands
| 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 |
Role Details
CEO (Meta-Layer) and Router
- 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 /ceo when the question genuinely needs synthesis. "One sharp lens beats three blurry ones"
Strategy & Management
- 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"
Security & Legal
